Connect your editor · MCP config
Use LinkedCamp in Cursor, Windsurf and Zed
Last updated:
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.
{ "mcpServers": { "linkedcamp": { "url": "https://mcp.linkedcamp.com/mcp", "headers": { "X-Api-Key": "YOUR_API_KEY" } } }}Setup
How do I add LinkedCamp to Cursor?
Add a linkedcamp entry to ~/.cursor/mcp.json with the URL https://mcp.linkedcamp.com/mcp and an X-Api-Key header holding your LinkedCamp API key. Windsurf and Zed take the same URL and header in their own MCP configuration. Then ask the assistant in your editor to call whoami, which reports your plan and permissions.
{
"mcpServers": {
"linkedcamp": {
"url": "https://mcp.linkedcamp.com/mcp",
"headers": {
"X-Api-Key": "YOUR_API_KEY"
}
}
}
}Menu names and config locations vary by editor version. Any client must support remote MCP over Streamable HTTP plus OAuth or authenticated headers.
When is an editor the right place for LinkedCamp?
When you're building around your outreach rather than just running it: internal tools, n8n flows or data pipelines that read campaign results. Your editor's assistant can query campaigns, analytics and leads while you write the code, and any change that reaches a prospect still asks for your confirmation first.
FAQ
Cursor, Windsurf and Zed and LinkedCamp: questions
Is the API key in mcp.json safe?
Can I use OAuth sign-in instead of a header?
Which LinkedCamp plan do I need?
Run LinkedCamp from your editor.
Start a 14-day free trial, connect your editor, and ask for your first campaign.