Why agents use this
- Auto-discovery is the MCP promise. Users type a URL, tools appear. That’s it.
- One endpoint, whole product. As you add tools to the server, they show up in every connected client on the next reload.
- Registry crawlers hit this. Smithery, mcp.so, and PulseMCP index MCP servers by fetching this manifest.
- Verify MCP compliance. Curl the endpoint before submitting to a registry to confirm the shape is right.
Use cases
- Add to Claude Desktop in 2 lines of config. Users edit
claude_desktop_config.json, restart, and get every Solana tool. - Cursor for Solana development. AI-assisted coding sessions with live on-chain lookups baked in.
- Custom agent framework (Eliza, Rig, ai16z) integration. Framework fetches the manifest, wires tools into the agent’s tool loop.
- MCP registry submission. Point Smithery, mcp.so, or PulseMCP at your gateway URL; they crawl the manifest and list you.
- Client compatibility check. Third-party MCP clients validate the manifest shape here before showing your server as usable.
Recipe: Claude Desktop configuration
Add this toclaude_desktop_config.json, then restart Claude Desktop.
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json