The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Abm MCP listing page.
The account-based marketing API for AI agents.
Search, Enrich, and Create across B2B people and companies — every field cited with a source and confidence score. One key, ten sources, no per-field bills.
https://mcp.abm.dev/mcpabm.dev is the account-based marketing API for AI agents. One key, one schema, four verbs:
search_companies, search_contacts.source, get_source.create_enrichment, get_enrichment_fields, get_enrichment_sources.create_company, create_contact, create_outreach; queue_linkedin_post stages a post for human approval — it never auto-publishes.Every value carries its source and a confidence score (0–1). A value is cited or it is not returned. No fabricated facts.
source and confidence (0–1), with the winning source that produced it.No per-source bills. No per-field charges. No silent fallbacks.
https://mcp.abm.dev/mcpThen ask, in plain language: "Find the VP of Marketing at Acme, then enrich them."
One install wires both the connector and the abm.dev Agent Skill — no URL pasting:
OAuth sign-in happens on first tool use. See claude-plugin/.
These agents drive the REST API directly. Paste this prompt:
Read https://abm.dev/llms.txt. Request an API key, save it to
.envasABM_API_KEY, then run a test enrichment againsthttps://api.abm.dev/v1/enrichments. Report the result with its citations.
Call the REST API directly:
input also accepts a LinkedIn URL or a company domain.
Prefer a local command over a remote URL? The @abmdev/mcp package is a thin
bridge: npx -y @abmdev/mcp launches a local STDIO MCP server that proxies to the
hosted server at https://mcp.abm.dev/mcp, handling the OAuth 2.1 PKCE sign-in
and token caching for you. It defines no tools of its own — it exposes whatever
the hosted server serves.
Add it to any MCP client that supports command/args (Claude Desktop,
Cursor, Windsurf, Claude Code, and others):
Generic config snippet (for clients that take a bare command):
On first run a browser window opens for the one-time sign-in; the token is then
cached for subsequent runs. Point the bridge at a different endpoint by setting
the ABM_MCP_URL environment variable.
Either path reaches the same hosted server. Use the custom connector (remote URL) above if your client supports it directly; use npx for clients that only speak local
command/args.
Grouped by verb — every field comes back with its source and confidence (0–1). Real-time SSE streaming for agent loops; webhooks fire when batch jobs finish.
Search — search_companies, search_contacts: find accounts and people by criteria.
Source — source, get_source: give it an account, get the right people back (async brief).
Enrich — create_enrichment, get_enrichment, get_enrichment_fields, get_enrichment_sources: cited, multi-source fields on a person (from an email or LinkedIn URL) or a company (from a domain).
Create — create_company, create_contact, create_outreach, queue_linkedin_post: write CRM records and stage outreach. Staged posts wait for human approval; nothing publishes automatically.
Per-enrichment. No subscription. Credits never expire. All ten sources included — no add-ons.
From about €0.29 per enrichment. Packs: 30 credits €2.89, 100 €9.29, 500 €36.99 (best value), 2,000 €119.99. The playground is free. Free launch credits with code LAUNCHCODES.
This repo is the public description of a hosted MCP server. The server runs at https://mcp.abm.dev/mcp; this repo is not its source. See server.json for the machine-readable manifest.
Questions or a stuck enrichment? Open a ticket: https://abm.dev
Foxley Farm Operations Ltd · UK Company No. 16392009 · Oakham, United Kingdom. GDPR-compliant.