abm.dev

abm.dev MCP server

Account-based marketing enrichment for AI agents.
One endpoint. Cited, multi-source fields. Every value attributed.

Hosted server: https://mcp.abm.dev/mcp
Homepage: https://abm.dev
For agents (machine-readable): https://abm.dev/llms.txt

What abm.dev is

Account-based marketing for AI agents. Give it an email, a LinkedIn URL, or a company domain; get back a structured record on the person and the company they work for. Every value carries its source, a confidence score, and a last-verified timestamp. A value is cited or it is not returned. No fabricated facts.

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.
Citations on every value — source, confidence (0–1), and freshness (last-verified timestamp).

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

Connect

Claude (custom connector)

Open Settings → Connectors → Custom.
Paste the server URL: https://mcp.abm.dev/mcp
Complete the one-time sign-in when prompted.

Then ask, in plain language: "Enrich jane@acme.com."

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

The server exposes enrichment:

Enrich a person — from an email or a LinkedIn URL. Returns the forty-three person fields plus the company they work for.
Enrich a company — from a domain. Returns the forty-six company fields.

Every field comes back with its source, confidence, and freshness. Real-time SSE streaming for agent loops; webhooks fire when batch jobs finish.

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.

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.

abm mcp