Short answer: mint an API key from your Abmatic AI dashboard, add https://mcp.abmatic.ai/mcp as a connector in claude.ai or Claude Code with the key as a bearer credential, and ask your first question. The whole setup takes about five minutes. Not a customer yet? Book a demo and we will do it live on real data.
Quick answer
How do I connect Claude to Abmatic AI? The Abmatic AI MCP server is a remote Model Context Protocol server at
https://mcp.abmatic.ai/mcpusing the Streamable HTTP transport. All three Claude surfaces connect the same way: supply your account'sabm_API key as a bearer token. In claude.ai you add a custom connector, in Claude Code you run oneclaude mcp addcommand, and in the Agent SDK you register the server with a static bearer credential. Once connected, Claude discovers 28 read-only tools covering your accounts, contacts, campaigns, revealed visitors, and analytics.
Key takeaways
- One server, three clients. claude.ai, Claude Code, and the Claude Agent SDK all connect to the same URL with the same key.
- Auth is a bearer header.
Authorization: Bearer abm_your_key_here. The key comes from your dashboard and is shown once at creation. - Everything is read-only. Connected agents can query data but can never write, update, or delete anything.
- Keys are managed, not permanent. Rotate or revoke from the dashboard with immediate effect; each key is rate limited to 100 requests per minute and audit logged.
- A paid plan is required. API keys are available on paid Abmatic AI plans; a valid key on a non-paid plan is rejected.
What your agent gets access to
Abmatic AI is the most comprehensive AI-native ABM platform, and the MCP server reads across all of it: the accounts and contacts produced by account-level deanonymization and contact-level deanonymization, campaigns from web personalization and A/B testing, sequences from Agentic Outbound, conversations from Agentic Chat, first-party intent and engagement scores, and the sync state of your bi-directional Salesforce or HubSpot connection. One connection, the whole picture.
Step 1: Get your Abmatic AI API key
The MCP server authenticates with an account-scoped API key of the form abm_...:
- Sign in to the dashboard at
app.abmatic.ai. - Go to Account, API Key.
- Click Generate (or Rotate). The full key is shown once, at creation time. Copy it immediately into a password manager or your agent's secret store; after you leave the page, only the key prefix is ever shown again.
- To revoke a key, use Delete on the same page. Rotating revokes the old key and returns a new one.
Treat the key like a password. It grants read access to your account's exposed data regardless of per-user dashboard roles, so keep it out of prompts, code, and shared docs. If it may have leaked, rotate it; revocation is immediate. Not seeing the API Key page? It ships with paid plans, so talk to us about upgrading.
Step 2a: Connect claude.ai
- In claude.ai, open Settings, Connectors and choose Add custom connector.
- Set the connector URL to
https://mcp.abmatic.ai/mcp. - When asked for authentication, choose the API key or bearer token option and paste your
abm_key. - Save. Claude connects, discovers the Abmatic AI tools, and lists them.
Confirm it works by asking: "Which Abmatic AI account am I connected to?" That calls the whoami tool and returns your account name, website, and plan tier.
Skip the manual work
Abmatic AI runs targets, sequences, ads, meetings, and attribution autonomously. One platform replaces 9 tools.
See the demo →Step 2b: Connect Claude Code
One command adds the server. The --transport http flag selects Streamable HTTP and the header carries your key:
claude mcp add --transport http abmatic https://mcp.abmatic.ai/mcp \
--header "Authorization: Bearer abm_your_key_here"Inside Claude Code, run /mcp to verify the abmatic server is listed with its tools. Then try "list my hot accounts" or "which companies did we de-anonymize this week". This is the setup most teams use for scheduled jobs, like a morning reveal digest posted to Slack.
Step 2c: Connect the Agent SDK or Managed Agents
Register the server as a Streamable HTTP MCP server with a static bearer credential stored in the agent vault:
- MCP server URL:
https://mcp.abmatic.ai/mcp - Transport: streamable HTTP
- Credential type:
static_bearer, valueabm_your_key_here
The agent runtime attaches the stored bearer to every request. Keep the key in the vault, not in code or prompts. This is the path for autonomous workflows: overnight account research, pre-call briefs, and pipeline monitoring that runs without a human in the loop. Our account research playbook shows what those workflows look like in practice.
Step 3: Ask your first questions
Good first prompts that exercise different parts of the surface:
- "Which companies visited our site this week that we have not contacted?" (reveal + contacts)
- "Show me accounts with an engagement score above 80, sorted by most recently active." (accounts with filters)
- "How is the enterprise personalization campaign performing?" (campaign analytics)
- "Is our CRM sync healthy?" (sync status)
For the complete list of all 28 tools and what each returns, see the Abmatic AI MCP server launch post. And if you want this running against your own traffic and pipeline, book a demo.
The Tier 1 tools you will use first
| Tool | What it does | First prompt to try |
|---|---|---|
whoami | Confirms the connection; returns account id, name, website, plan tier. | "Which Abmatic AI account am I connected to?" |
list_accounts | Companies tracked for you, with fit, engagement, and overall scores. | "List my top 20 accounts by engagement." |
get_account | One company by website or id. | "What do we know about acme.com?" |
list_contacts | People, scoped to a company or filtered by name or email. | "Who do we know at Acme?" |
list_campaigns | Your campaigns, optionally by status. | "Which campaigns are live right now?" |
get_campaign | One campaign's configuration and summary. | "Describe the enterprise ABM campaign." |
get_campaign_analytics | Performance metrics for one campaign. | "How did it perform last month?" |
list_revealed_companies | Companies de-anonymized from recent website traffic. | "Who visited us this week?" |
get_analytics_summary | Account-level rollup: visitors, reveals, engagement. | "Summarize this month's website activity." |
Troubleshooting
| Symptom | Cause and fix |
|---|---|
| 401 unauthorized | The key is missing, blank, unknown, or revoked. Re-check the Authorization: Bearer abm_... header and mint a fresh key if needed. |
| 403 forbidden | The key is valid but the account is not on a paid plan. |
| 429 rate limited | You exceeded 100 requests per minute. The server returns a retry hint and honors Retry-After; back off and retry. |
| Empty reveal results with a note | Reveal is not enabled on your plan. Expected behavior, not an error. |
| Tool not found | Your client may only have the Tier 1 surface; Tier 2 tools roll out over time. |
Still stuck? Grab time with our team and we will debug the connection together, or start from the MCP server overview. Teams comparing agent-ready platforms should also read our take on the best AI agents for ABM and API-native ABM platforms.
FAQ
How do I connect Claude to Abmatic AI?
Add https://mcp.abmatic.ai/mcp as a custom connector in claude.ai, or run claude mcp add with the transport http flag in Claude Code, supplying your Abmatic AI API key as a bearer credential. Claude discovers the tools automatically.
Where do I find my Abmatic AI API key?
In the dashboard at app.abmatic.ai under Account, API Key. Click Generate or Rotate; the full key is shown once at creation, so copy it into a password manager immediately.
Does the connection require OAuth?
No. Today you authenticate with your API key as a bearer token. A browser-based login option is coming, but the API key path is the supported method right now.
Can I connect agents other than Claude?
Yes. Any MCP client that supports the Streamable HTTP transport and bearer authentication can connect to the server, including agents built on the Claude Agent SDK and Managed Agents.
Is it safe to give an autonomous agent this access?
The surface is read-only, account-scoped, rate limited to 100 requests per minute, and audit logged. Agents can query data but can never modify campaigns, contacts, settings, or CRM sync.
Why am I getting a 403 from the MCP server?
A 403 means your key is valid but your account is not on a paid plan. API keys and MCP access are features of paid Abmatic AI plans; book a demo to get set up.
What should I ask first to test the connection?
Ask "Which Abmatic AI account am I connected to?" That calls the whoami tool, which confirms the key works and returns your account name, website, and plan tier.
Want this live on your own pipeline? Book a demo and we will connect Claude to your account during the call.
