aep

The AEP MCP Server generates MCP resources and tools from an AEP-compliant API. It reads your API’s OpenAPI specification and exposes MCP resources that mirror your API’s entities, along with MCP tools to create, update, or delete those resources. This enables clients to interact with your API through the MCP layer, leveraging Model Context Protocol tooling for resource management and discovery. You can inspect available resources using the inspector tool to verify how MCP resources map to your API endpoints.

To use the server locally, install dependencies and start the server using the provided npm script. You can then access the generated MCP resources according to the OpenAPI you supply. The inspector utility can be run to validate and explore the MCP surface that the server provides, helping ensure your MCP resources align with your API structure.

Prerequisites:

• Node.js and npm installed on your machine
• Access to the repository (clone from GitHub)

Installation steps:

1. Clone the repository

   • git clone https://github.com/aep-dev/aep-mcp-server.git
   • cd aep-mcp-server

2. Install dependencies

   • npm install

3. Run the server (examples)

   • npm run serve --openapi-url="http://localhost:8081/openapi.json" This starts the MCP server using the provided OpenAPI document.
   • If you need to target a different OpenAPI source or a Cloud prefix, you can use: npm run serve --openapi-url="https://raw.githubusercontent.com/Roblox/creator-docs/refs/heads/main/content/en-us/reference/cloud/cloud.docs.json" --prefix="/cloud/v2"

4. Optional direct execution with npx (when installed locally or globally):

   • npx . --openapi-url="http://localhost:8081/openapi.json"

Notes:

• Ensure the OpenAPI URL you provide is accessible from the server host.
• The server will generate MCP resources based on the API definitions in the OpenAPI document.

Tips and notes:

• The inspector tool can be used to explore MCP resources generated from your API: npx @modelcontextprotocol/inspector node src/bin.js --openapi-url="http://localhost:8081/openapi.json".
• If you update your API’s OpenAPI document, restart the MCP server to refresh the generated MCP resources.
• Make sure the OpenAPI document defines the resources you expect to be exposed as MCP resources; verify paths, schemas, and operations align with MCP capabilities.
• Environment variables are not required by default, but you can introduce options for API base URLs, authentication tokens, or custom mapping rules as needed by your deployment environment.