Reach MCP

About Reach MCP

Reach MCP is an MCP server that gives AI agents and agencies hands-on control of LinkedIn accounts for prospecting, messaging, and engagement. It runs on the Kanbox infrastructure trusted by 2,000+ agencies and powers the LinkedIn automation capabilities behind Kanbox, having sent 2M+ messages and created 3M+ connections.

Users can connect LinkedIn accounts through a Chrome extension without sharing passwords, then plug into Claude, ChatGPT, Cursor, or automation platforms like n8n and Make using a single connector URL. The platform ships with eight built-in playbooks such as turning post reactions into leads, finding profile viewers, managing cold conversations, and conducting Sales Navigator searches.

Every action that writes messages, invitations, or comments shows a numbered preview first with the person, context, and exact text, waiting for approval before sending one at a time within daily limits. Reach MCP includes a rotating proxy, automatic daily rate-limit management, and per-account security for agencies managing multiple client accounts.

• agencies
• linkedin
• automation
• prospecting
• sales
• mcp
• ai agents

FAQ

Can my AI send messages without me seeing them?

No. Every playbook that writes shows a numbered preview first with the person, context, and exact text, and waits for you to approve which ones to send. Messages, invitations, and comments are sent one at a time within your account's daily limits. Read-only playbooks like your week in review and profile research run without touching anything.

Which LLMs are supported?

Any system that speaks MCP (Model Context Protocol) is supported, including Claude, ChatGPT, Cursor, and automation platforms like n8n, Make, and Zapier. Claude and ChatGPT connect via OAuth with a single URL, while automation platforms use the same URL with an API key. There is also a documented REST API for custom integrations.

Can I manage my clients' LinkedIn accounts?

Yes. Agencies typically use Reach MCP for this purpose. Send each client a branded invite link where they connect their LinkedIn from a page with your agency's name and logo, without sharing a password. Each account has its own residential proxy, its own daily limits, its own action log, and sits behind the same MCP URL and API. You can restrict an API key to one client's accounts.

Does Reach MCP comply with LinkedIn's Terms of Service?

Reach MCP is designed to respect LinkedIn's daily limits and reduce risky activity patterns. Activity is paced within LinkedIn's daily limits with a rotating proxy and human-behavior simulation. However, LinkedIn automation still carries real account risk—new, fake, or low-trust accounts are more likely to be flagged.

How is my access secured?

Two layers secure access. Your Reach MCP account credentials, access keys, and OAuth tokens are encrypted and stored securely. Reach MCP connects to LinkedIn through the Chrome extension using your existing LinkedIn session—you do not share your LinkedIn password with Reach MCP, and uninstalling the extension revokes access. The infrastructure is hosted in Europe.