Gives AI agents the same account intelligence a great B2B rep used to keep in their head. Point it at an email, LinkedIn URL, or company domain and get back 89 canonical fields across person and company records. Every value ships with its source, a confidence score, and a last-verified timestamp. It pulls from ten providers including LinkedIn, Companies House, Perplexity, and Tavily, then resolves everything into one cited response. Works over streamable HTTP or stdio. Reach for it when you're building agent workflows that need to qualify leads, enrich CRM records, or research accounts without stitching together multiple enrichment APIs yourself.
Account-based marketing enrichment for AI agents.
One endpoint. Cited, multi-source fields. Every value attributed.
https://mcp.abm.dev/mcpAccount-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.
source, confidence (0–1), and freshness (last-verified timestamp).No per-source bills. No per-field charges. No silent fallbacks.
https://mcp.abm.dev/mcpThen ask, in plain language: "Enrich jane@acme.com."
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:
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.
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.
The server exposes enrichment:
Every field comes back with its source, confidence, and freshness. Real-time SSE streaming for agent loops; webhooks fire when batch jobs finish.
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.
cyanheads/git-mcp-server
io.github.b1ff/atlassian-dc-mcp-bitbucket
com.mcparmory/atlassian-jira
sirlordt/vscode-terminal-mcp
aashari/mcp-server-atlassian-bitbucket
sooperset/mcp-atlassian