API contract (openapi.json) — MapMap MCP Resource

API contract (openapi.json) is one of 7 resources on the MapMap MCP server. Connect the server and your client can attach it as context.

by client

How to attach API contract (openapi.json) from your client

• Claude Code MapMap Resource/API contract (openapi.json) run in your project directory
• Claude Desktop MapMap Resource/API contract (openapi.json) ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor MapMap Resource/API contract (openapi.json) ~/.cursor/mcp.json
• VS Code MapMap Resource/API contract (openapi.json) .vscode/mcp.json
• Zed MapMap Resource/API contract (openapi.json) ~/.config/zed/settings.json
• Windsurf MapMap Resource/API contract (openapi.json) ~/.codeium/windsurf/mcp_config.json
• Cline MapMap Resource/API contract (openapi.json) ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI MapMap Resource/API contract (openapi.json) ~/.gemini/settings.json
• Grok MapMap Resource/API contract (openapi.json) .mcp.json (in your project root)
• ChatGPT MapMap Resource/API contract (openapi.json) Settings → Connectors → Advanced → Developer mode
• Claude.ai MapMap Resource/API contract (openapi.json) Settings → Connectors → Add custom connector
• LangChain MapMap Resource/API contract (openapi.json) pip install langchain-mcp-adapters

Other resources on this server

• Deployment orientation (llms.txt)
• ADR tunnel-code reference
• Measured clearance reference
• Agent skills index
• Routing mode (this instance)
• Route map

MapMap also offers 2 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.