MCP.so
ログイン

Reach MCP Server認証済み注目

@Kanbox

基本情報

トランスポート

Streamable HTTP

認証方式

OAuth

カテゴリ

AI とエージェント

作者

Kanbox

投稿者

Jean Carriere

Reach MCP Server について

Operate a real LinkedIn account from your AI agent. 52 tools for the inbox, invitations, network, profiles, Sales Navigator search in plain language, posts and engagement; six playbooks served as MCP prompts that preview before they write; daily quotas enforced server-side; structured errors; idempotent writes; signed webhooks when a prospect replies or a connection is accepted. LinkedIn only. 7-day trial, no card. Docs for agents: https://www.reachmcp.com/llms.txt

接続情報

https://app.reachmcp.com/mcp

セットアップ

claude mcp add reach-mcp --transport http https://app.reachmcp.com/mcp

Reach MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

このサーバーは認証が必要です。ツールの取得にはログインや提供元の認証情報が必要な場合があります。

上のボタンでサーバーのエンドポイントに接続し、ツール一覧を取得できます。

概要

Reach MCP lets an AI agent operate a real LinkedIn account from Claude, ChatGPT, Cursor, n8n, Make or your own code: read and answer the inbox, send invitations, search Sales Navigator in plain language, publish and engage with posts — with the controls an agent needs around every call. LinkedIn only, by design.

Quick start

{ "mcpServers": { "reach": { "url": "https://app.reachmcp.com/mcp" } } }
  1. Sign up at https://app.reachmcp.com/signup and connect a LinkedIn account with the Chrome extension (your own session; no password is typed into Reach; uninstalling revokes access).
  2. Add the server to your client. Ask: "What can you do with my LinkedIn?" — the reach_playbooks tool returns six ready-made workflows.
  3. Run one: "Find my LinkedIn conversations that went cold and draft a follow-up for each." Every playbook that writes shows a numbered preview and waits for your go.

What the agent gets — 52 tools

AreaTools
Start herereach_playbooks
Inboxlist_conversations, list_conversation_messages, send_message, react_message, star_conversation, archive_conversation, delete_conversation
Sales Navigator inboxsalesnav_list_messaging_threads, salesnav_list_thread_messages, salesnav_send_message
Networklist_connections, connect, invitation_status, withdraw_invitation, accept_invitation, decline_invitation, remove_connection, follow, list_received_invitations, list_sent_invitations
Profiles & searchscrape_profile, scrape_search, visit_profile, profile_viewers, salesnav_resolve_industry, salesnav_typeahead, salesnav_build_search_url
Posts & engagementuser_posts, scrape_post, scrape_my_posts, like_post, comment_post, reply_comment
Publishingcreate_post, list_scheduled_posts, update_scheduled_post, delete_scheduled_post, upload_media_from_url, create_multi_photo
Accounts & quotaslist_accounts, get_me, get_account_quotas, update_account_quotas, get_account_request_logs, get_account_request_logs_stats, delete_account
Webhookslist_webhook_endpoints, create_webhook_endpoint, update_webhook_endpoint, delete_webhook_endpoint, test_webhook_endpoint

Every tool carries MCP annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint), a description on every parameter, and an output schema.

Six playbooks, served as MCP prompts

  • My LinkedIn week in review — activity, rotting invitations, waiting conversations (read-only).
  • Wake up cold conversations — threads where you spoke last and nobody answered, with a draft follow-up each.
  • Turn post reactions into leads — everyone who liked or commented on your posts, qualified and messaged.
  • Turn profile viewers into leads — the people who checked you out, scored and given an opener.
  • Reply to every comment — a real answer to each comment on your recent posts, in the commenter's language.
  • A prospect list from one sentence — "heads of sales at French SaaS companies" becomes a real Sales Navigator search, the rows, and a personalised invitation each.

Built for agents, not just for calls

  • Daily quotas enforced server-side — invitations, messages, visits, imports, posts, comments, reactions each have a per-account limit checked before every write. Exceed it and the call is refused with daily_quota_reached and the reset time. An agent told to "message everyone" cannot.
  • Errors an agent can act on — every failure carries a stable code, safe_to_retry, retry_at and a remediation sentence; MCP failures are isError results, not protocol errors.
  • Idempotent writes — pass idempotency_key on any write; a retry after a timeout never sends twice.
  • Signed webhooks — message.received, connection.new, account.status_changed, quota.threshold_reached, quota.reached. Stripe-style HMAC signature, retries for 15 hours, replay from the dashboard. Your n8n or Make workflow reacts instead of polling.
  • Natural-language Sales Navigator search — industries resolved against LinkedIn's taxonomy, geographies and companies against live autocomplete, disambiguation when a term is ambiguous.
  • Residential proxy per account and human-like pacing.

Also available as REST

Base https://app.reachmcp.com/api, header X-API-Key. Interactive reference: https://app.reachmcp.com/scalar · OpenAPI: https://app.reachmcp.com/openapi.json

Pricing

  • Standard — for a person running their own LinkedIn from Claude or ChatGPT: $39/month for one account, graduated down to $12.
  • Builder — for agencies and products built on the API/MCP: $10 per account for 1–4, $7 for 5–10, $6 for 11–50, $5 from 51. Ten accounts: $70/month.

Every feature in both plans. Monthly, no commitment. https://www.reachmcp.com/#pricing

Honest about risk

Reach MCP is not an official LinkedIn API: it relies on the account owner's authenticated session and LinkedIn's internal interfaces. LinkedIn automation carries real account risk; the proxy, the enforced limits and the pacing reduce it, nothing removes it. Data is processed in the EU (Google Cloud, europe-west1); session cookies are stored encrypted and removed when the account is deleted. https://www.reachmcp.com/docs/security.md

Built by the team behind Kanbox (2,000+ teams, 2 million LinkedIn messages sent). Support: hello@reachmcp.com

よくある質問

1

Reach MCP のリモート MCP サーバーとは何ですか?

Reach MCP のリモート MCP サーバーは、https://app.reachmcp.com/mcp にホストされた Model Context Protocol エンドポイントです。AI アシスタントはローカルに何もインストール・実行することなく接続できます。

2

Reach MCP の MCP サーバーにはどう接続しますか?

エンドポイント https://app.reachmcp.com/mcp を Claude Code、Cursor、VS Code など任意の MCP 対応クライアントに追加してください。このページのセットアップ手順で各クライアントを一度に設定できます。

3

Reach MCP の MCP サーバーは認証が必要ですか?

はい。Reach MCP は OAuth を使用します。初回接続時に MCP クライアントがブラウザを開いてサインイン・認可を行い、以降はその認証情報を再利用します。

4

Reach MCP の MCP サーバーはどのトランスポートを使用しますか?

Reach MCP は Streamable HTTP エンドポイントを公開しており、これはリモート MCP サーバーで広く使われ、主要な MCP クライアントがサポートするトランスポートです。

コメント