Ask Claude where your competitors are active.
Connect the Deal Intelligence MCP server, and Claude answers with verified competitor activity: named buyers and named competitors, matched to your own accounts. Hosted, read-only, one sign-in.
Named answers, not summaries.
Claude reads verified competitor activity: the buyer, the competitor and the date, checked on both sides. It doesn’t infer them from scraped pages or intent scores.
- Competitor evaluations. “Who started talking to a competitor this week?”
competitive_activity - Deals at-risk. “Which open deals have a competitor in them?”
pipeline_at_risk - Closed-lost revivals. “Which closed-lost accounts are back in market?”
closed_lost_revival - Renewals at-risk. “Which renewals have a buyer talking to a competitor?”
renewals_at_risk
Eleven tools. All read-only.
Claude starts with discover, then picks the tool that fits the question. Every call is scoped to your accounts.
| Tool | What it answers |
|---|---|
discover | Your real competitor, owner and industry names, so Claude asks with them. |
competitive_activity | Verified activity across your accounts: which buyer is talking to which competitor. |
account_activity | Everything at one account: buyers, competitors, timeline and any open opportunity. |
buyer_activity | Everything about one buyer, across every employer. |
pipeline_at_risk | Open deals where a competitor is in the deal, joined with your CRM. |
renewals_at_risk | Renewals where a buyer is talking to a competitor. |
closed_lost_revival | Closed-lost accounts with new competitor activity. |
churn_risk | Customers in active competitor conversations. |
top_accounts | Your accounts ranked by competitor activity. |
multi_competitor_accounts | Accounts with more than one competitor active. |
competitor_summary | Every account where one competitor is active. |
Connect it your way.
Add the hosted server in Claude, or point Claude Code at it. Either way you always run the latest version.
- Claude connector. Settings, then Connectors, then Add custom connector. Paste the server URL and sign in with your Deal Intelligence account. No API key is stored in Claude.
- Claude Code. Point at the same server over HTTP and authenticate with an API key from your account settings.
- Read-only. Every tool reads. The connector never writes to your CRM, changes a record or sends outreach.
- Ask here. Always-on everywhere else. Claude is where you ask, and you decide what to do with the answer. The same activity runs Always-on in your CRM, Clay and Slack, routed to the owner and added to your campaigns every morning.
- Your plan. The MCP server is on every plan. Access requires an active plan.
Every plan includes the MCP server and every other delivery surface. Unlimited seats, so the whole team can ask.
Compare plansExplore FAQs
What does the MCP server give Claude?
How do we connect it to Claude?
https://api.dealintelligence.io/mcp and sign in with your Deal Intelligence account. For Claude Code, point at the same server over HTTP with an API key. See the MCP docs.Can Claude write to our CRM?
Can Claude research one account?
account_activity to return its buyers, the competitors they’re in contact with, the timeline and any open opportunity.How fresh is the data?
How is it different from intent data?
How do we start?
Turn your competitors’ pipeline into yours.
Runs on your own account list. The guarantee: new pipeline, or a competitor found in one of your open deals.
Start a 30-day pilot with an ROI guarantee.