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