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.
@aep-dev
基本信息
暂无概览
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"mcpServers": {
"aep-mcp-server": {
"command": "npx",
"args": [
"@modelcontextprotocol/inspector",
"node",
"src/bin.js",
"--openapi-url=http://localhost:8081/openapi.json"
]
}
}
}工具列表暂未提供
当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。
点击上方按钮,在临时沙箱中运行此服务器并实时获取工具列表。
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.
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.
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.
Clone the repository from GitHub and run `npm install` in the project directory.
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.
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.
Yes, you can provide a `--prefix` argument to set a path prefix that will be applied to all generated MCP operations.

Persistent memory for AI agents. Hosted MCP server with capsule-scoped key/value storage, tags, TTL expiration, bulk ops, and RBAC.

Mess in, magic out: pour in your D&D and TTRPG notes and LoreKeeper keeps them as a private store for your world. Ask Claude or ChatGPT about it, or build a sourcebook.

Serve your docs to AI agents over SSH and MCP. Agents use ls, cat, grep, find, and pipes against a virtual filesystem backed by your documentation. Identity-scoped access, governed writing with human approval, and portab

One permissioned folder your team and your AI agents both log into.

Ask your Takibi Base collections anything; get answers with cited passages and a support score.
评论