MCP Server
MCP Server
Connect AI assistants (Cursor, Claude, VS Code, ChatGPT, Windsurf) to APIpie documentation using the Model Context Protocol (MCP).
What This MCP Server Provides (Today)
APIpie exposes a read-only MCP server that allows AI tools to:
- Discover documentation pages
- Fetch page content
This MCP server is documentation-only. It does not provide live platform APIs, routing execution, provider metadata, pricing, or write access.
MCP Endpoint
Use this MCP server URL:
https://apipie.ai/mcp
Available Tools
list-pages
Lists all available documentation pages (title, path, description).
| Parameter | Type | Description |
|---|---|---|
locale | string (optional) | Filter pages by locale |
get-page
Retrieves full markdown for a specific page.
| Parameter | Type | Description |
|---|---|---|
path | string (required) | Page path (e.g. /routing/overview) |
What This MCP Server Does NOT Do
To avoid confusion for agent systems:
- No model routing or execution
- No provider/model inventory
- No pricing/quotas
- No account access
- No mutations (create/update/delete)
- No prompts (yet)
If it’s not listed under Available Tools, it does not exist.
Connect an AI Client
ChatGPT (Custom Connector)
- Open ChatGPT Settings
- Go to Connectors
- Enable Developer mode (if required)
- Create a New Connector
- Name:
APIpie Docs - MCP Server URL:
https://apipie.ai/mcp - Authentication:
None
- Name:
- Save
You can then enable the connector in a conversation and ask:
- “List APIpie docs pages”
- “Fetch the page for
/routing/overviewand summarize it”
Claude Code
claude mcp add --transport http apipie-docs https://apipie.ai/mcp
Claude Desktop
- Open Claude Desktop → Settings → Developer
- Click Edit Config
- Add:
{
"mcpServers": {
"apipie-docs": {
"command": "npx",
"args": ["mcp-remote", "https://apipie.ai/mcp"]
}
}
}
- Restart Claude Desktop
Cursor
Quick Install
If your environment supports MCP deep links, add the server in Cursor via Settings → Tools & MCP using:
- Name:
apipie-docs - Type:
http - URL:
https://apipie.ai/mcp
Manual Setup
Create or edit:
.cursor/mcp.json
{
"mcpServers": {
"apipie-docs": {
"type": "http",
"url": "https://apipie.ai/mcp"
}
}
}
Visual Studio Code
Create or edit:
.vscode/mcp.json
{
"servers": {
"apipie-docs": {
"type": "http",
"url": "https://apipie.ai/mcp"
}
}
}
Ensure you have GitHub Copilot + Copilot Chat installed if you want Copilot to use it.
Windsurf
- Open Windsurf → Settings → Cascade
- Manage MCPs → View raw config
- Add:
{
"mcpServers": {
"apipie-docs": {
"type": "http",
"url": "https://apipie.ai/mcp"
}
}
}
Zed
Add to your Zed settings JSON:
{
"context_servers": {
"apipie-docs": {
"source": "custom",
"command": "npx",
"args": ["mcp-remote", "https://apipie.ai/mcp"],
"env": {}
}
}
}
Validate It Works
After connecting, ask your assistant:
- “Call
list-pagesand show me the first 10 results.” - “Call
get-pagefor the routing overview page and summarize it.”
If those work, the MCP connection is correct.
Usage Examples (Docs-Only)
Once configured, AI assistants can reliably do:
- “List all APIpie documentation pages”
- “Get the authentication page and extract required headers”
- “Find the docs page describing routing fallbacks”
- “Retrieve the webhook docs and summarize event payloads”
Anything involving live routing, models, or account state requires APIpie’s API (not MCP).