Setup guides
Connect your AI assistant
Last updated:
One remote endpoint for every client. Pick yours for the exact steps, or add https://mcp.linkedcamp.com/mcp to any client that supports remote MCP servers.
- Endpoint
https://mcp.linkedcamp.com/mcp- Transport
- Streamable HTTP
- Auth
- OAuth 2.1 + PKCE (enter your LinkedCamp API key) · or X-Api-Key / Bearer header
- Tools
- 133 — 64 read-only · 69 that change data · 28 of them destructive (they ask first)
Compatibility
Which AI assistants can connect to LinkedCamp?
LinkedCamp works with ChatGPT through its published plugin and with any client that supports remote MCP over Streamable HTTP plus OAuth or authenticated HTTP headers. That includes Claude, Claude Code, Cursor, Windsurf, Zed and OpenClaw, which have guides below. Availability depends on each provider's plan, workspace policy and current MCP support.
ChatGPT
Install the published LinkedCamp plugin, sign in with your API key, and ask ChatGPT to build, check and report on your campaigns.
Setup guide →Claude
Add one custom connector, sign in with your LinkedCamp API key, and run your LinkedIn and email outreach from a Claude chat.
Setup guide →Claude Code
Register LinkedCamp's remote MCP server from the terminal, authenticate with an X-Api-Key header, and work on campaigns and reports without leaving your editor.
Setup guide →Cursor, Windsurf and Zed
Add one server entry to your editor's MCP config with your LinkedCamp API key as a header. The same remote endpoint works in every editor that supports Streamable HTTP MCP servers.
Setup guide →OpenClaw
Register LinkedCamp's MCP server in OpenClaw, sign in once with your LinkedCamp API key, and run outreach from any chat OpenClaw is on.
Setup guide →Gemini
Grok
HermesDocs ↗Grok Bot
Muse
Add the endpoint wherever the runtime accepts remote Streamable HTTP MCP servers. Availability depends on the client's plan.
Client table on /mcp →Connect once. Ask for anything.
Start a 14-day free trial, add LinkedCamp to your assistant and ask for your first campaign.