catalog_sources — Sugra API MCP Resource

catalog_sources is one of 8 resources on the Sugra API MCP server. Connect the server and your client can attach it as context.

by client

How to attach catalog_sources from your client

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

Other resources on this server

• catalog_domains
• attribution
• skill_explore_catalog
• skill_envelope_attribution
• skill_auth_limits
• skill_hosted_vs_gateway
• skill_cross_domain_briefing

Sugra API also offers 6 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.