Skip to main content

LinkedCamp for Claude

Build campaigns, work the inbox and pull analytics from a Claude chat. There is no config file to edit.
LinkedCamp is listed in Claude’s Connectors Directory. You connect it once on the web or desktop, and it then works in every Claude chat on web, desktop and mobile.

What it connects to

The same hosted server every other client uses:
Transport is Streamable HTTP. Authentication is OAuth 2.1 with PKCE: Claude opens a LinkedCamp sign-in page and you paste your API key, which is the only credential that page accepts. The key is encrypted inside the access token and never appears in a URL or a log line.

Connect it

1

Find LinkedCamp in the directory

Open LinkedCamp in Claude, or go to Settings → Connectors, choose Browse connectors, and search for LinkedCamp. On a Team or Enterprise plan, an owner may need to enable it for the organization first.
2

Connect

Open the LinkedCamp listing and click Connect.
3

Choose an access tier and sign in

Claude opens the LinkedCamp sign-in page. Pick Full access, Read and write or Read only, then paste your API key from Settings → Integrations. The key is checked right away, so a typo fails on this page and not mid-conversation.
4

Use it

In a new chat, turn LinkedCamp on from the tools menu and ask: “List my active campaigns and tell me which one has the best reply rate.”

Can’t find it in the directory?

Add the same server as a custom connector instead. It uses the same sign-in and the same tools.
  1. In Settings → Connectors, choose Add custom connector.
  2. Name it LinkedCamp and paste https://mcp.linkedcamp.com/mcp. Leave the advanced OAuth fields empty.
  3. Sign in as in step 3 above.
If you added LinkedCamp as a custom connector before the directory listing, it keeps working. You don’t need to switch.

Access tiers

The tier you choose at sign-in applies to that connection for as long as it lasts: To change the tier, remove the connector and add it again. See access tiers for the details.

Claude asks before anything irreversible

Every tool is marked as reading, writing or destructive. Claude can run read-only tools without asking, depending on your connector permission settings. Destructive tools, such as launching a campaign, sending a message or deleting a record, show a confirmation in Claude every time. You can tighten this per tool in Settings → Connectors → LinkedCamp, for example by setting every write tool to Always ask.
campaign_set_status with ACTIVE restarts real outreach on a paused campaign. It counts as a write and not as destructive, because pausing again undoes it, so Claude may not prompt for it. Say “ask me before resuming anything” if you want a confirmation.

Plan and permission limits apply

The connector reaches the same surface as any other client. Pro-only steps refuse on plan grounds, and sections your user permissions do not grant are hidden. Ask Claude to call whoami if a refusal is unclear. Agency owners get the sub-account reach described in MCP for agencies.

Disconnect

  • Remove the connector in Claude under Settings → Connectors.
  • Cut off every connection at once by rotating your API key in Settings → Integrations. Every token issued with the old key stops working immediately, in Claude and in every other client.

Claude Code

Claude Code can use the same OAuth flow, or it can send the key as a header with no browser step:
See the quickstart for Cursor, Windsurf, Zed and local stdio.