A proxy per account
Each LinkedIn account uses its own residential proxy.
Every write runs on the account you named, against the daily limit you set for that kind of action. Reach the limit and the action stops with its reset time.
7-day trial · no credit card to start.
Same controls onLinkedInSales NavigatorRecruiter
ReachMCP is not an official LinkedIn API. It acts from the account owner's own LinkedIn session, and LinkedIn can still restrict an account.
When one account reaches its daily invitation limit, its invitation batch pauses. Other actions and accounts keep working within their own limits.
Each LinkedIn account uses its own residential proxy.
Choose when each account's batches can run.
Batch actions are spaced out instead of sent together.
An API key can be restricted to the accounts you select. Every LinkedIn action is logged under the account that performed it, with its time and its outcome, so a result or an error stays where it belongs.
Review drafts in your AI assistant, or add an approval step to your own workflow.
Your assistant proposes the drafts, you pick the ones to send, and only those go out.
Your workflow prepares the post or message, waits for a person to approve it, then calls ReachMCP.
For mandatory approval, configure a review step in your own workflow.
No. ReachMCP works from the account owner's own LinkedIn session, not an official API. You get a proxy, enforced daily limits and paced batches; LinkedIn can still restrict an account.
You do. Each kind of action ships with a default, and the account owner changes it in the app or through the API. These are ReachMCP limits, not LinkedIn's published ones.
It pauses, records why, and continues inside the next working window. A direct call is stopped instead, with its reset time — nothing is queued for it.
Only if you let it. An API key can be restricted to the accounts you select, and a call aimed at an account outside that key is refused.
7-day trial · no credit card to start.