Advertise
MCP.so
Sign In

Readme MCP Server

@aep-dev

Repository

Basic information

Category

Memory & Knowledge

License

Apache-2.0

Transports

stdio

Author

aep-dev

About Readme MCP Server

No overview available yet

#aep-mcp-server#server#development

Readme MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "aep-mcp-server": {
      "command": "npx",
      "args": [
        "@modelcontextprotocol/inspector",
        "node",
        "src/bin.js",
        "--openapi-url=http://localhost:8081/openapi.json"
      ]
    }
  }
}

Readme MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

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.

Frequently asked questions

1

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.

2

How do I install the AEP MCP Server?

Clone the repository from GitHub and run `npm install` in the project directory.

3

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.

4

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.

5

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.

Comments

More Memory & Knowledge MCP servers

Tempreon

Tempreon

Person-owned, portable AI memory served over MCP. Your knowledge, preferences, and decisions — captured in one assistant, available in all of them.

Orcha

westonhancock

Orcha is a unified context layer for AI tools and agents. It stores and indexes and exposes organizational, team, or individual knowledge. Files, structured databases, and connected sources live in one workspace, and age

Azquo

Azquo Holdings Ltd

Exact, shared memory for AI agents: a hierarchical database where totals always add up, every write is attributed to the agent and person behind it, and any figure traces back to its source file. Agents create databases,

M1K3

Round-Tower

Local AI agent for your Mac with a built-in MCP server: 18 tools for your notes and PDFs, a temporal memory graph, an on-device LLM and a neural voice. No account, no telemetry. No data centers required.

7

Snipara

alopez3006

MCP connector for Snipara, the Project Brain for AI coding agents

1
Advertise