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