abm.dev MCP server

• Hosted server: https://mcp.abm.dev/mcp

• Homepage: https://abm.dev

• For agents (machine-readable): https://abm.dev/llms.txt

What your agents can do

abm.dev is the account-based marketing API for AI agents. One key, one schema, four verbs:

• Search — find companies and people by criteria. search_companies, search_contacts.

• Source — hand it a target account, get the right buying-committee people back. Async briefs: source, get_source.

• Enrich — cited, multi-source fields on any person or company. create_enrichment, get_enrichment_fields, get_enrichment_sources.

• Create — write CRM records and stage outreach. 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.

Related MCP server: LeadEnrich MCP Server

What you get

• Eighty-nine canonical fields per record — forty-three on the person, forty-six on the company.

• Forty signals on every prospect.

• Ten sources, resolved into one response — LinkedIn, Companies House, Perplexity, Tavily, Hunter, and others.

• A citation on every value — source and confidence (0–1), with the winning source that produced it.

No per-source bills. No per-field charges. No silent fallbacks.

Connect

Claude (custom connector)

1. Open Settings → Connectors → Custom.

2. Paste the server URL: https://mcp.abm.dev/mcp

3. Complete the one-time sign-in when prompted.

Then ask, in plain language: "Find the VP of Marketing at Acme, then enrich them."

Claude Code (plugin)

One install wires both the connector and the abm.dev Agent Skill — no URL pasting:

/plugin marketplace add abm-dev-git/abm-mcp
/plugin install abm-dev@abm-dev

OAuth sign-in happens on first tool use. See claude-plugin/.

Cursor / Claude Code / Windsurf

These agents drive the REST API directly. Paste this prompt:

Read https://abm.dev/llms.txt. Request an API key, save it to .env as ABM_API_KEY, then run a test enrichment against https://api.abm.dev/v1/enrichments. Report the result with its citations.

Script and terminal agents

Call the REST API directly:

curl https://api.abm.dev/v1/enrichments \
  -H "x-api-key: $ABM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"type":"person","input":{"email":"jane@acme.com"}}'

input also accepts a LinkedIn URL or a company domain.

Install (npx)

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):

{
  "mcpServers": {
    "abm": {
      "command": "npx",
      "args": ["-y", "@abmdev/mcp"]
    }
  }
}

Generic config snippet (for clients that take a bare command):

{ "command": "npx", "args": ["-y", "@abmdev/mcp"] }

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.

Tools

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.

Pricing

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.

See https://abm.dev/#pricing.

Links

• Homepage: https://abm.dev

• For agents (llms.txt): https://abm.dev/llms.txt

• Docs: https://abm.dev/docs · Getting started

• API reference: https://abm.dev/api-reference · Enrichment · Jobs

• For developers: https://abm.dev/for-developers · For agents: https://abm.dev/for-agents · For marketers: https://abm.dev/for-marketers

• Integrations: Claude connector · HubSpot · Notion · Slack

• Concepts: Enrichment · Confidence scores · Data sources · Canonical fields

• Sign up: https://abm.dev/sign-up · Free playground: https://abm.dev/dashboard/playground

Registry reference

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.

Support

Questions or a stuck enrichment? Open a ticket: https://abm.dev

Operator

Foxley Farm Operations Ltd · UK Company No. 16392009 · Oakham, United Kingdom. GDPR-compliant.