Skip to main content
abm.dev
5 minInstall guide

Install the connector

Add the ABM.dev connector to Claude.ai and grant it access to your workspace in about two minutes.

Before you start

  • A Claude.ai account with access to Custom Connectors (Pro / Team / Enterprise).
  • An ABM.dev workspace (sign up free if you don't have one).
  • A browser — you'll complete a short OAuth flow on abm.dev.
1

Open Claude's connector settings

In Claude.ai, open Settings → Connectors and click Add custom connector.

Screenshot placeholder — Claude.ai Settings → Connectors → Add custom connector

2

Paste the MCP server URL

Name the connector ABM.dev and paste this into the MCP server URL field:

MCP server URL
https://mcp.abm.dev/mcp

TLS still provisioning?

If Claude reports it can't reach mcp.abm.dev, our TLS certificate is still rolling out. Use the Railway fallback URL instead — it works immediately and points at the same service:
https://mcp-server-production-883e.up.railway.app/mcp

Click Add. Claude will discover the OAuth endpoints automatically, register itself as an OAuth client via RFC 7591 Dynamic Client Registration, and kick off the sign-in flow.

Screenshot placeholder — Custom connector URL field with mcp.abm.dev pasted

3

Sign in on abm.dev

Claude opens a new window that redirects you to https://abm.dev/sign-in. If you're already signed in to ABM.dev in this browser, it skips straight to consent.

Sign in with the same email you use for ABM.dev. We use Clerk for authentication — Claude never sees your password.

Screenshot placeholder — abm.dev/sign-in Clerk login screen

4

Grant consent

You'll see a consent screen that looks like this:

Claude.ai wants to access ABM.dev as:
  you@example.com
  Your Workspace
Requested access:
  • abm:read — read enrichments, campaigns, jobs
  • abm:write — create enrichments, confirm campaigns, approve results
  • abm:linkedin — use your connected LinkedIn for tools
  • abm:enrich — spend enrichment credits
  • abm:generate — generate and publish content

Click Allow. Claude is redirected back with an authorization code, exchanges it for an access token (PKCE S256), and the connector shows as Connected.

Screenshot placeholder — consent screen with Allow / Deny

5

Try your first prompt

Open a new Claude chat and paste any of these to confirm the connector is working:

Use ABM.dev to list my last 5 enrichment jobs.
Use ABM.dev to enrich john@acme.com with LinkedIn.
Find the CTO and Head of Engineering at linear.app using ABM.dev.

Claude will ask for permission

The first time Claude calls any tool, it shows the tool name, arguments, and asks for your approval. You can approve just this call, or all future calls of that tool for this chat.

How to disconnect

You can revoke the connector at any time:

  • From Claude.ai: Settings → Connectors → ABM.dev → Remove. This deletes the stored tokens on Claude's side.
  • From ABM.dev: Settings → Connected apps → Revoke. This invalidates all outstanding refresh tokens for your user.

Next steps

Authentication details

What scopes really mean.

Tools reference

All 81 tools Claude can call.