get_competitor_intel — zero core intel MCP Tool Read-only
get_competitor_intel
(get competitor intel) is one of 8 tools on the
zero core intel
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_competitor_intel from your client
- Claude Code zero core intel get_competitor_intel run in your project directory
- Claude Desktop zero core intel get_competitor_intel ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor zero core intel get_competitor_intel ~/.cursor/mcp.json
- VS Code zero core intel get_competitor_intel .vscode/mcp.json
- Zed zero core intel get_competitor_intel ~/.config/zed/settings.json
- Windsurf zero core intel get_competitor_intel ~/.codeium/windsurf/mcp_config.json
- Cline zero core intel get_competitor_intel ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI zero core intel get_competitor_intel ~/.gemini/settings.json
- Grok zero core intel get_competitor_intel .mcp.json (in your project root)
- ChatGPT zero core intel get_competitor_intel Settings → Connectors → Advanced → Developer mode
- Claude.ai zero core intel get_competitor_intel Settings → Connectors → Add custom connector
- LangChain zero core intel get_competitor_intel pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http zero-core-intel https://agents.rugslayer.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.