Troubleshooting
If the connector is misbehaving, start here. Most issues come down to DNS, session cookies, or scope mismatches.
Quick self-test
Before anything else, verify the MCP endpoint is reachable:
curl -i -X POST https://mcp.abm.dev/mcp \
-H 'Content-Type: application/json' \
-d '{}'
# Expected:
# HTTP/1.1 401 Unauthorized
# WWW-Authenticate: Bearer realm="https://mcp.abm.dev",
# error="invalid_token",
# resource_metadata="https://mcp.abm.dev/.well-known/oauth-protected-resource"A 401 with the WWW-Authenticate header is the correct, healthy response for an unauthenticated request. If you get a 5xx, a timeout, or a TLS error, move to the fallback URL below.
Common issues
Claude says 'Couldn't connect to MCP server'
Likely cause
- Our TLS cert for mcp.abm.dev is still provisioning.
- A corporate proxy is blocking *.abm.dev.
- You typed the URL with a trailing slash or without /mcp.
Fix
Use the Railway fallback URL, which skips our managed TLS and works immediately:
https://mcp-server-production-883e.up.railway.app/mcpThe exact path must end with /mcp — not / and not /mcp/.
Sign-in page loads, but clicking 'Allow' bounces back to sign-in
Likely cause
- Your browser is blocking third-party cookies on abm.dev.
- You opened the connector flow in a private/incognito window that expired the Clerk session between redirects.
Fix
Open abm.dev in the same browser and confirm you're signed in. Then retry "Add custom connector" from Claude. Disable strict tracking prevention for abm.dev and clerk.abm.dev if using Safari or Brave.
After signing in, you see: 'You are signed in as ... but no ABM.dev workspace is attached to this account.'
Likely cause
- Your Clerk user exists but has no organisation yet.
- You signed in with a secondary email that isn't linked to your workspace.
Fix
Go to abm.dev and create or join a workspace. Then retry the connector install.
If you work across multiple orgs, make sure the correct organisation is selected in the ABM.dev header before starting the OAuth flow.
Claude reports 'Unauthorized' when calling any tool
Likely cause
- Access token expired and refresh failed (Clerk session gone / connector revoked).
- Someone revoked the connector from ABM.dev Settings → Connected apps.
Fix
In Claude: Settings → Connectors → ABM.dev → Reconnect. You'll briefly re-authorise on abm.dev; this issues a fresh refresh token.
If the reconnect itself fails, remove the connector and add it again from scratch.
LinkedIn tools return 'no LinkedIn account connected'
Likely cause
- You haven't connected a LinkedIn account to your ABM.dev workspace yet.
- Your LinkedIn cookies expired (li_at usually lasts ~1 year, but LinkedIn can revoke early).
Fix
Head to Settings → LinkedIn and connect or reconnect. Then retry in Claude. See the full LinkedIn connection guide.
Claude says 'I don't have access to that tool'
Likely cause
- The tool is gated by a scope you didn't grant (e.g. abm:linkedin not approved).
- Claude.ai blocked the tool via its own per-chat allowlist.
Fix
In Claude: Settings → Connectors → ABM.dev, review which tools are enabled. Click Reconnect to re-approve scopes if a new one has been added since your original grant.
An enrichment starts but Claude never shows the result
Likely cause
- Claude's streaming buffer timed out on a long enrichment.
- Model output truncation hid the result summary.
Fix
Ask Claude: "List my last enrichment job and show its result." The job was created server-side even if the streamed preview cut off — you can fetch it by ID.
Consent screen shows 'invalid_target' after sign-in
Likely cause
- Claude registered with a resource parameter that doesn't match our canonical URI.
- You manually edited the OAuth URL.
Fix
Remove the connector from Claude.ai and re-add it without modifying the URL. We require resource=https://mcp.abm.dev(exact match, RFC 8707). Claude sets this automatically when you use the mcp.abm.dev URL.
Still stuck?