teardown_tech_stack — Klarix Intelligence Engine MCP Tool
teardown_tech_stack
(teardown tech stack) 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 teardown_tech_stack from your client
- Claude Code Klarix Intelligence Engine teardown_tech_stack run in your project directory
- Claude Desktop Klarix Intelligence Engine teardown_tech_stack ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Klarix Intelligence Engine teardown_tech_stack ~/.cursor/mcp.json
- VS Code Klarix Intelligence Engine teardown_tech_stack .vscode/mcp.json
- Zed Klarix Intelligence Engine teardown_tech_stack ~/.config/zed/settings.json
- Windsurf Klarix Intelligence Engine teardown_tech_stack ~/.codeium/windsurf/mcp_config.json
- Cline Klarix Intelligence Engine teardown_tech_stack ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Klarix Intelligence Engine teardown_tech_stack ~/.gemini/settings.json
- Grok Klarix Intelligence Engine teardown_tech_stack .mcp.json (in your project root)
- ChatGPT Klarix Intelligence Engine teardown_tech_stack Settings → Connectors → Advanced → Developer mode
- Claude.ai Klarix Intelligence Engine teardown_tech_stack Settings → Connectors → Add custom connector
- LangChain Klarix Intelligence Engine teardown_tech_stack 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
- get_competitor_battlecard
- 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
- 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.