catalog_status — Dajsve MCP Resource

catalog_status is one of 2 resources on the Dajsve MCP server. Connect the server and your client can attach it as context.

by client

How to attach catalog_status from your client

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

Other resources on this server

• offer_categories

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.