Abm Mcp

io.github.abm-dev-gitPublished by GitHub account abm-dev-gitv1.0.3Updated Oct 27, 2026

abm.dev — the account-based marketing API for AI agents: Search, Enrich, and Create across B2B.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

abm.dev's account-based marketing API for AI agents: search, source, enrich and create B2B company and contact records with cited fields.

What you can do
  • Search companies and contacts by criteria
  • Source buying-committee people for a target account via async briefs
  • Enrich a person or company with multi-source fields, each carrying a source and confidence score
  • Create CRM records and stage outreach, including LinkedIn posts held for human approval
  • Retrieve enrichment fields and their underlying sources
When to use it
Useful when an assistant needs to research B2B accounts, find or verify contact and company details with citations, or draft and stage outreach and CRM records from a chat or agent workflow.
Requirements
Remote endpoint at mcp.abm.dev, or the npm package @abmdev/mcp run with npx as a local stdio bridge to that endpoint. OAuth sign-in is required; the bridge opens a browser for a one-time sign-in and caches the token. The ABM_MCP_URL variable can point the bridge at another endpoint. Paid credits are needed for enrichments.
Before you install
Enrichment is billed per call from prepaid credit packs, so agent loops can spend money. Create tools write CRM records and stage outreach; staged LinkedIn posts wait for human approval and do not publish automatically. Enrichment sends personal data such as emails, LinkedIn URLs and company domains to abm.dev and its ten external data sources.

Installation

In SourceWeft

  1. Open Abm Mcp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.abm-dev-git%2Fabm-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "abm": {
      "type": "http",
      "url": "https://mcp.abm.dev/mcp"
    }
  }
}

README

[abm.dev]

abm.dev MCP server

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.

[npm] [MIT] [MCP] [Smithery]

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.

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:

bash
curl https://api.abm.dev/v1/enrichments \  -H "x-api-key: $ABM_API_KEY" \  -H "Content-Type: application/json" \  -d '{"type":"person","input":{"email":"[email protected]"}}'

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

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

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

json
{ "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

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.

Source: README.md at commit d3fe9e9

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.3LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts