api-catalog — api MCP Resource
api-catalog
is one of 4 resources on the
api
MCP server. Connect the server and your client can attach it as context.
by client
How to attach api-catalog from your client
- Claude Code api Resource/api-catalog run in your project directory
- Claude Desktop api Resource/api-catalog ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor api Resource/api-catalog ~/.cursor/mcp.json
- VS Code api Resource/api-catalog .vscode/mcp.json
- Zed api Resource/api-catalog ~/.config/zed/settings.json
- Windsurf api Resource/api-catalog ~/.codeium/windsurf/mcp_config.json
- Cline api Resource/api-catalog ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI api Resource/api-catalog ~/.gemini/settings.json
- Grok api Resource/api-catalog .mcp.json (in your project root)
- ChatGPT api Resource/api-catalog Settings → Connectors → Advanced → Developer mode
- Claude.ai api Resource/api-catalog Settings → Connectors → Add custom connector
- LangChain api Resource/api-catalog pip install langchain-mcp-adapters
Other resources on this server
api also offers 1 prompt — 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.