generate_outreach_sequence — Klarix Intelligence Engine MCP Tool
generate_outreach_sequence
(generate outreach sequence) 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 generate_outreach_sequence from your client
- Claude Code Klarix Intelligence Engine generate_outreach_sequence run in your project directory
- Claude Desktop Klarix Intelligence Engine generate_outreach_sequence ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Klarix Intelligence Engine generate_outreach_sequence ~/.cursor/mcp.json
- VS Code Klarix Intelligence Engine generate_outreach_sequence .vscode/mcp.json
- Zed Klarix Intelligence Engine generate_outreach_sequence ~/.config/zed/settings.json
- Windsurf Klarix Intelligence Engine generate_outreach_sequence ~/.codeium/windsurf/mcp_config.json
- Cline Klarix Intelligence Engine generate_outreach_sequence ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Klarix Intelligence Engine generate_outreach_sequence ~/.gemini/settings.json
- Grok Klarix Intelligence Engine generate_outreach_sequence .mcp.json (in your project root)
- ChatGPT Klarix Intelligence Engine generate_outreach_sequence Settings → Connectors → Advanced → Developer mode
- Claude.ai Klarix Intelligence Engine generate_outreach_sequence Settings → Connectors → Add custom connector
- LangChain Klarix Intelligence Engine generate_outreach_sequence pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http intelligence https://mcp.klarix.ai/mcp
Other tools on this server
- find_matched_prospects
- score_prospect_fit
- get_competitor_battlecard
- analyze_head_to_head
- get_company_intelligence
- 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.