axiom-capability-registry — Axiom Relay MCP Resource

axiom-capability-registry is one of 1 resource on the Axiom Relay MCP server. Connect the server and your client can attach it as context.

by client

How to attach axiom-capability-registry from your client

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

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.