get_competitor_battlecard — Klarix Intelligence Engine MCP Tool Read-only
get_competitor_battlecard
(get competitor battlecard) is one of 15 tools on the
Klarix Intelligence Engine
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_competitor_battlecard from your client
- Claude Code Klarix Intelligence Engine get_competitor_battlecard run in your project directory
- Claude Desktop Klarix Intelligence Engine get_competitor_battlecard ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Klarix Intelligence Engine get_competitor_battlecard ~/.cursor/mcp.json
- VS Code Klarix Intelligence Engine get_competitor_battlecard .vscode/mcp.json
- Zed Klarix Intelligence Engine get_competitor_battlecard ~/.config/zed/settings.json
- Windsurf Klarix Intelligence Engine get_competitor_battlecard ~/.codeium/windsurf/mcp_config.json
- Cline Klarix Intelligence Engine get_competitor_battlecard ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Klarix Intelligence Engine get_competitor_battlecard ~/.gemini/settings.json
- Grok Klarix Intelligence Engine get_competitor_battlecard .mcp.json (in your project root)
- ChatGPT Klarix Intelligence Engine get_competitor_battlecard Settings → Connectors → Advanced → Developer mode
- Claude.ai Klarix Intelligence Engine get_competitor_battlecard Settings → Connectors → Add custom connector
- LangChain Klarix Intelligence Engine get_competitor_battlecard pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http intelligence https://mcp.klarix.ai/mcpOther tools on this server
- find_matched_prospects
- score_prospect_fit
- analyze_head_to_head
- get_company_intelligence
- generate_outreach_sequence
- generate_swot_analysis
- get_deep_research
- search_scientific_evidence
- get_market_landscape
- get_buying_committee
- detect_account_triggers
- teardown_tech_stack
- generate_displacement_playbook
- teardown_product_spec
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.