API Status — Agent Module MCP Resource

API Status is one of 3 resources on the Agent Module MCP server. Connect the server and your client can attach it as context.

by client

How to attach API Status from your client

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

Other resources on this server

• OpenAPI Specification
• ROI Calculator

Agent Module also offers 3 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.