3 min readIntegration

Claude.ai Custom Connector

Give Claude direct access to your ABM.dev workspace. Enrich contacts, find people, run campaigns, and drive LinkedIn activity — all through a conversation.

Screenshot placeholder — Claude.ai connector settings

What it is

The ABM.dev Custom Connector is a Model Context Protocol (MCP) server that plugs into Claude.ai. Once installed, Claude can call your ABM.dev tools on your behalf — with your consent — to enrich contacts, run campaigns, post to LinkedIn, and more.

It speaks the official MCP Authorization spec (2025-06-18): OAuth 2.1 with PKCE, Dynamic Client Registration, and audience-bound access tokens. No API keys to copy and paste. Just click "Add connector," sign in once, and Claude is wired to your workspace.

MCP server URL

https://mcp.abm.dev/mcp

Tools exposed

81 tools

TLS still provisioning

The canonical URL https://mcp.abm.dev/mcp is the production endpoint, but TLS provisioning may still be in-flight. Until it's finalised, use the Railway fallback URL: https://mcp-server-production-883e.up.railway.app/mcp. Claude discovers OAuth metadata automatically from either.

What you get

Enrichment on demand

"Enrich jane@acme.com" runs LinkedIn, Hunter, Perplexity, and Tavily — Claude streams the result back in under a minute.

People finder

"Find the Head of Engineering at Stripe" — candidate discovery with confidence scores.

Campaign orchestration

Preview, launch, and approve ABM campaigns from the Claude chat. Results write back to HubSpot.

LinkedIn actions

Search profiles, view feed activity, post, comment, send connection requests and messages — all through your connected account.

How it works

The connector lives at mcp.abm.dev. When Claude first connects, it runs through a one-time OAuth flow:

1.Claude.ai fetches our OAuth metadata and registers itself via Dynamic Client Registration.
2.You're redirected to abm.dev/sign-in to authenticate with Clerk.
3.You see a consent screen showing your email, workspace, and requested scopes. Click Allow.
4.Claude receives a short-lived access token bound to mcp.abm.dev. It can now call tools on your behalf.

No API keys to manage

You never need to copy, paste, or rotate an API key. Tokens expire in 1 hour, refresh automatically, and can be revoked at any time from your ABM.dev settings.

Things you can ask Claude

Use ABM.dev to enrich sarah@company.com with LinkedIn and Hunter

Find the CTO and VP Engineering at linear.app

Preview a campaign for these 10 companies targeting Head of Ops

Pull my LinkedIn feed from the last 24 hours and summarise it

Post this article to my LinkedIn with commentary: <url>

Show me the last 5 enrichment jobs and their confidence scores

Ready to install?

The full install walkthrough takes about 2 minutes.

Install the connector

In this section

Install guide

Add the connector to Claude.ai, step by step.

Authentication

OAuth flow, scopes, and what consent grants.

Tools reference

Every tool Claude can call, grouped by category.

Troubleshooting

Sign-in failures, missing workspace, 401s.

Developer reference

.well-known URLs, DCR endpoint, canonical resource URI, test curl commands.