概要
What is AEP MCP Server?
AEP MCP Server is a Model Context Protocol server that automatically generates MCP resources and tools from an AEP-compliant API. It is designed for API developers who have built APIs following the AEP (aep.dev) specification, enabling those APIs to be exposed through MCP for reading, listing, creating, updating, and deleting resources.
How to use AEP MCP Server?
Clone the repository and install dependencies with npm install. Then run the server locally using npm run serve --openapi-url="<url>" or npx . --openapi-url="<url>". Optionally provide a --prefix argument to set a path prefix for all generated operations.
Key features of AEP MCP Server
- Generates MCP resources and tools from any AEP-compliant OpenAPI specification.
- Supports read and list operations on API resources as MCP resources.
- Provides MCP tools for creating, updating, and deleting API resources.
- Works with local or remote OpenAPI URLs.
- Accepts an optional path prefix for custom operation grouping.
Use cases of AEP MCP Server
- Exposing an AEP-compliant REST API as MCP resources and tools for AI assistants.
- Allowing LLMs to browse, create, update, and delete resources through a standardized protocol.
- Rapidly integrating any existing AEP API with the Model Context Protocol without manual code generation.
- Prototyping MCP‑based tooling for APIs that follow the AEP design patterns.
FAQ from AEP MCP Server
What is an AEP‑compliant API?
AEP (AEP.dev) is a set of API design patterns and guidelines. An AEP‑compliant API follows those patterns. Visit aep.dev for full details.
How do I install the AEP MCP Server?
Clone the repository from GitHub and run npm install in the project directory.
How do I run the server?
Use npm run serve --openapi-url="<url>" or, if installed globally, npx . --openapi-url="<url>". You can also add --prefix="/custom/path" to modify the generated operation paths.
What does the server generate?
It generates MCP resources for reading and listing API resources, and MCP tools for creating, updating, and deleting those resources – all based on your AEP‑compliant OpenAPI document.
Can I customize the generated operations?
Yes, you can provide a --prefix argument to set a path prefix that will be applied to all generated MCP operations.
