Linkedcamp

com.linkedcampPublished by linkedcamp.comOfficial publisherv1.0.3Updated Nov 3, 2026

LinkedIn and email outreach: campaigns, unified inbox, leads, analytics and reports.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration Data & Analytics Business & Commerce

Server details

Identifier: com.linkedcamp/mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Nov 3, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to linkedcamp.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.linkedcamp%2Fmcp.svg)](https://sourceweft.com/mcp/com.linkedcamp%2Fmcp?utm_source=readme&utm_medium=badge)

Overview

Linkedcamp's hosted MCP server (mcp.linkedcamp.com), published by linkedcamp.com; OAuth sign-in required; Streamable HTTP.

No AI overview yet: these facts come from the registry entry and the server itself.

Publisher: linkedcamp.com
Endpoint: mcp.linkedcamp.com
Documentation: docs.linkedcamp.com
Last checked: Nov 3, 2026

Installation

In SourceWeft

Open Linkedcamp in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
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/com.linkedcamp%2Fmcp/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": {
    "linkedcamp": {
      "type": "http",
      "url": "https://mcp.linkedcamp.com/mcp"
    }
  }
}

README

[LinkedCamp]

LinkedCamp MCP server

Run LinkedIn and email outreach from ChatGPT, Claude, Cursor or any MCP client.
[LinkedCamp MCP connector] [mcptry]

Documentation · Product page · Support

LinkedCamp is LinkedIn and email outreach for lead-gen agencies. This is its official hosted MCP server: build and launch campaigns, write multi-step sequences, triage the unified inbox, manage prospects and pull client reports — all from an AI assistant.

Nothing to install and nothing to run. The server is hosted by LinkedCamp; you point your client at one URL.


Transport	Streamable HTTP (remote)
Auth	OAuth 2.1 with PKCE and dynamic client registration, or an `X-Api-Key` header
Tools	133 across 14 groups — 64 read-only, 69 write, 28 flagged destructive
Requires	A LinkedCamp Pro or Agency plan. 14-day free trial.
Registry	`com.linkedcamp/mcp`

Connect

Claude

Settings → Connectors → Add custom connector, then paste the URL above and sign in. Claude handles OAuth for you.

ChatGPT

Install the LinkedCamp app from the ChatGPT directory, or add the URL above as a custom connector. Sign-in is the same OAuth flow.

Cursor, VS Code, Windsurf and other config-file clients

Claude Code

Without OAuth

Any client that can set a header may send your API key directly instead of running the OAuth flow:

Your key is under Settings → Integrations in LinkedCamp. Treat it as a password: it carries the same access your account has.

What you can do with it

Group	Tools	What it covers
`core`	3	Orientation — the plan, permissions and the enum vocabulary
`campaigns`	19	Create, configure, source prospects, launch, and manage once live
`flows`	9	Author the sequence a campaign runs, and see how each step performs
`leads`	14	Prospects, their history, and the scheduled actions behind it
`accounts`	13	The LinkedIn accounts and mailboxes campaigns send from, and their limits
`inbox`	9	LinkedIn and email conversations — where replies land and are answered
`analytics`	5	Performance by campaign, sending account and whole account
`library`	20	Tags, exclusion rules, saved copy, merge fields, blocked dates
`personas`	5	Ideal-customer definitions a `QUALIFIER` step scores leads against
`agents`	13	Agents that reply to prospects and book meetings, and their knowledge base
`content`	6	LinkedIn posts: drafting, scheduling and the publishing calendar
`crm`	7	Connected CRMs and manual follow-up around a conversation
`automation`	4	Account-wide, event-driven workflows
`settings`	6	Notifications, profile preferences and the team roster

Full reference: docs.linkedcamp.com/mcp/overview

Safety

Outreach reaches real people, so the server is built to make that visible rather than convenient.

28 tools are annotated destructive. Clients surface that in their approval prompt, so a human confirms before anything is deleted or sent. The set is wider than "it deletes something" — launching a campaign, sending a test email, and changing who gets messaged are all flagged, because each reaches outside the account or is hard to undo.
You choose what a connection may do when you sign in. Read only, Read and write, or Full access. Read only reaches the 64 tools that change nothing; Read and write adds ordinary writes but withholds the destructive ones; Full access reaches everything and still asks before each destructive call.
Your plan and team permissions still apply. A section you cannot open in the web app is hidden from the tool list and refused on the call.
Some things are deliberately not exposed at all: rotating your API key, connecting a LinkedIn account (that flow takes a password and a verification PIN), CRM credentials, and billing.

A smaller tool list

Some clients are slower to start against 133 tool definitions, because they read every one before answering anything. Name the groups you want:

Leaving it off gives you everything. core is always included, and an unrecognised name is ignored rather than leaving you with an empty connection.

Support

Documentation — docs.linkedcamp.com/mcp/overview
Troubleshooting — docs.linkedcamp.com/mcp/troubleshooting
Email — [email protected]

This repository holds the install documentation and client manifests only. The server itself is hosted by LinkedCamp and is not open source.

Source: README.md at commit cdb6929

Tools

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

v1.0.3LatestNov 3, 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