Your agent needs more than LinkedIn access. It needs a safe way to act.
Reach MCP runs LinkedIn workflows from AI agents: 52 tools, ready-made playbooks, daily quotas the server enforces, errors an agent can act on, idempotent writes and signed webhooks. A messaging pipe is not an agent platform.
7 days free, no card. Builder plan from $10 an account.
Works from
“The developer owns the cadence” is four projects
A messaging API gives your agent a way to send. It does not tell it when to stop, does not wake it up when the prospect answers, does not remember who was already contacted from another account, and does not stop a retry from sending the same message twice. Every team building on a raw API rebuilds those four things, usually after the first incident. Reach MCP ships them as the product.
From a sentence to controlled execution
The agent asks in plain language
"Find heads of sales at French SaaS companies, skip anyone contacted in the last 90 days, draft 20 invitations." Reach turns it into a real Sales Navigator search, resolves the ids, and returns the rows.
Reach previews, then acts inside the limits
Every playbook shows a numbered preview before it writes. Sends go out one at a time; the server refuses the 21st invitation of the day with a structured error and the time the quota resets.
Your workflow gets called when something happens
A reply lands, a connection is accepted, an account disconnects, a quota is nearly spent: Reach posts a signed webhook to n8n, Make or your own service. The agent reacts instead of polling.
For the people who read the response body
OAuth for MCP clients, an API key for everything else, one error shape everywhere, and an idempotency key on every write. The REST reference is public.
# Claude Desktop / Cursor / any MCP client — OAuth, nothing to paste
{ "mcpServers": { "reach": { "url": "https://api.reachmcp.com/mcp" } } }
# REST: one write, safe to retry
POST /api/linkedin/12/messages
Idempotency-Key: 6f1c… X-API-Key: mcp_…
{ "recipient_linkedin_id": "ACoAA…", "text": "Thanks for connecting, Ana." }
# When a quota is spent, the answer tells the agent what to do
429 { "error": { "code": "daily_quota_reached", "safe_to_retry": true,
"retry_at": "2026-09-11T00:00:00Z",
"remediation": "Stop this action on this account for today…" } }What a runtime adds that a pipedoesn't
Budgets the server enforces
Invitations, messages, visits, imports, posts, comments and reactions each have a daily limit per account, checked before every write. Exceed it and the call is refused with quota_reached and retry_at. An agent told to "message everyone" cannot.
An operating MCP, not a docs MCP
52 tools that act on the account, six playbooks served as MCP prompts, a "start here" tool for vague requests. Built for the person or agent operating LinkedIn from Claude, ChatGPT or n8n, not only for the developer writing integration code.
Errors an agent can act on
Every failure carries a stable code, whether a retry can help, when, and what to do instead. Every write accepts an idempotency key, so a timeout and a retry never send two messages.
One sentence to a Sales Navigator search
Describe who you want. Reach resolves industries against LinkedIn's taxonomy, geographies and companies against live autocomplete, asks when a term is ambiguous, and returns the search URL plus the first page of results.
How Reach MCP compares to Unipile
Both let software act on a real LinkedIn account through the user's own session. The difference is what sits around the calls. Unipile is a broad, multi-channel communications API with a developer-oriented MCP; Reach MCP is a LinkedIn-only runtime built for agents. Honest, like-for-like, dated.
Choose Unipile if your product needs one API across email, WhatsApp, Instagram and calendars, the widest set of low-level LinkedIn primitives (Recruiter projects, job postings, company pages, InMail credits), or hosted white-label authentication. Choose Reach MCP if your product or agency is centred on LinkedIn prospecting, recruiting or engagement and you want the limits, the errors, the playbooks and the events shipped rather than built.
Unipile capabilities per developer.unipile.com and unipile.com, as of 9 September 2026. Their marketing states built-in proxy rotation and quota management; their technical documentation states that no usage limits are enforced on their side. Both are quoted here.
Two ways to pay for accounts
Both bill by connected account, not by call. The difference is what the account price includes. With Reach MCP the runtime is in it: quotas, errors, idempotency, webhooks, playbooks and proxy are not things you build on top.
Reach MCP
- Builder plan: every account billed at the rate your total reaches. $10 for 1–4 accounts, $7 for 5–10, $6 for 11–50, $5 from 51. Ten accounts: $70 a month.
- Standard plan for a person running their own LinkedIn from Claude: $39 for one account, graduated down to $12.
- Every feature in every plan: tools, playbooks, quotas, proxy, webhooks, REST and MCP.
- Billed monthly, no commitment, cancel anytime. Switch plans until your first payment.
Unipile
- A monthly minimum that includes up to 10 connected accounts, then a per-account rate that steps down with volume.
- Post-paid on the peak number of simultaneously connected accounts in each 30-day period.
- All channels and endpoints included; usage itself is not metered.
Unipile pricing model per unipile.com/pricing, as of 9 September 2026.
Checkable on day one, priced for builders
The 101st message is refused
Ask for 300 messages on an account limited to 100 and the server stops at 100, every time, with the reset time in the error. That is a demo you can run on day one of the trial.
A reply wakes your workflow
Register an n8n or Make URL, get a signed POST when a conversation has a new unread message. Verified with the same HMAC scheme Stripe uses; retried for fifteen hours; replayable.
Your session, revocable
A Chrome extension uses the account owner's existing LinkedIn session. No password leaves the browser, and removing the extension revokes access.
Builder plan · every account at the rate your total reaches
Ten accounts: $70 a month. Fifty: $300. Tools, playbooks, quotas, proxy, webhooks, REST and MCP are all in the account price. Running your own LinkedIn from Claude instead? The Standard plan starts at $39.
Many clients, one runtime
Each client's account owner connects their own session through a link carrying your brand. API keys and webhooks are scoped to the accounts you choose. Quotas, logs and statistics are per account, so a report is a query, not a spreadsheet. Built on the infrastructure behind Kanbox: 2,000+ teams, 2 million messages sent.
Honest about risk and data
LinkedIn automation carries real account risk; new or fake accounts are the most exposed, and we never claim zero risk. Session cookies are stored encrypted and are removed when the account is deleted or the extension uninstalled. Every LinkedIn request is logged per account. Data is processed in the EU; the GDPR page lists processors and retention. Read the GDPR page.
Questions before you build
·Is Reach MCP an alternative to a multi-channel messaging API?
For agents and products centred on LinkedIn, yes. If your core requirement is one API spanning email, WhatsApp, Instagram and calendars, it is not: Reach does LinkedIn only, on purpose.
·Does Reach MCP use the official LinkedIn API?
No. Like every tool in this category, Reach relies on the account owner's authenticated session and LinkedIn's internal interfaces. Automation carries real account risk. A residential proxy, enforced daily limits and human-like pacing reduce it; nothing removes it, and we never claim otherwise.
·What exactly happens when a quota is reached?
The write is refused with HTTP 429, code daily_quota_reached, the count, the limit and the UTC time it resets. On MCP the tool returns an isError result carrying the same object. Other actions and other accounts keep working.
·Can an agent send without a human approving?
Through the API, yes: your code holds the key. The six playbooks always show a numbered preview and wait for the user to name what to send, and the daily limits apply regardless. A server-side approval policy per API key is in development; until it ships we do not describe approval as a technical guarantee.
·How do I connect my clients' accounts?
Each account owner installs the Chrome extension from a branded invitation link you send them, and authorises their own session. No password reaches you or us. You can scope API keys and webhooks to specific accounts.
·Can I migrate from another LinkedIn API?
Account, conversation and profile identifiers are LinkedIn's own, so most mappings are direct. Searches map to the Sales Navigator builder or to URL-based search. We do not promise a drop-in compatible endpoint; the REST reference is public and you can compare before you start.
Connect one account. Run one playbook. Watch the limits work.
Free for 7 days, no card. Agencies and product teams: book a 15-minute technical fit review.