FinchreachConnect your LinkedIn

Updated

Cursor logoAnysphere · Code editorConnects directly

What can Cursor do on LinkedIn with Finchreach?

Cursor can read your LinkedIn feed, messages and notifications, search LinkedIn, and draft posts, comments, messages and connection invitations through Finchreach’s remote MCP server. Add the server to Cursor and sign in to Finchreach (OAuth) or use your Finchreach API key; every write waits in your approval queue until you approve it.

Connect your LinkedIn Read the docs

What can Cursor do on your LinkedIn?

Cursor sees the project you’re working on, so the LinkedIn post about a release or the reply to a technical question can come from the code itself instead of a blank page. You stay in the editor; the approval happens in Finchreach.

Ask your assistant“Write a LinkedIn post about the refactor in this branch, aimed at other engineers.”
Ask your assistant“Search LinkedIn for people working on developer tools in Berlin and list them with their headlines.”
Ask your assistant“Draft replies to my unread LinkedIn messages; keep each under 60 words.”
Reads (run right away)Writes (wait for your approval)
linkedin_list_accounts: The LinkedIn accounts connected to your workspacelinkedin_create_post: A text post
linkedin_get_profile: A LinkedIn profilelinkedin_send_dm: A direct message
linkedin_get_feed: Your home feedlinkedin_send_invitation: A connection invitation, with an optional note
linkedin_get_notifications: Your notificationslinkedin_react_to_post: A reaction on a post (like by default)
linkedin_get_conversations: Your message threadslinkedin_unreact: Removes your reaction from a post
linkedin_get_messages: The messages in a threadlinkedin_comment_on_post: A comment on a post
linkedin_search: Search everything, posts, people or companieslinkedin_delete_comment: Deletes one of your comments
linkedin_get_received_invitations: Coming soon: the connection invitations waiting for your answerlinkedin_accept_invitation: Coming soon: accepts a received invitation
linkedin_get_action: The status of a write: waiting for approval, approved, rejected or done

What happens when Cursor drafts something?

  1. Cursor calls a write tool, for example linkedin_create_post with the text it wrote.
  2. Finchreach doesn’t post it. It stores a pending action and tells the assistant it is waiting for approval.
  3. You open Approvals, read the exact text and the account it would go out from, and approve or reject it.
  4. Approved actions run on LinkedIn; rejected ones never do. Cursor can check the outcome with linkedin_get_action.

Approval mode is on by default for every workspace. It is what makes it reasonable to let an assistant draft in your name.

Does Cursor work with Finchreach today?

Cursor
Remote MCP serversBuilt in
Finchreach (OAuth or API key)Connects directly
How sure we areHigh: from the official docs
Checked on2026-10-28

Headers are supported, with ${env:NAME} interpolation, so the Finchreach key goes in Authorization: Bearer.

Finchreach’s server, https://mcp.finchreach.com/mcp, uses Streamable HTTP (pasting the bare https://mcp.finchreach.com works too). It signs in with OAuth 2.1, where you log in to Finchreach and approve a LinkedIn account and scopes, or with an API key sent as Authorization: Bearer lk_… or X-API-Key.

How do I connect Cursor?

  1. Create an API key under API keys and connect your LinkedIn account under Accounts.
  2. Open .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project (Settings → MCP links to it too).
  3. Paste the entry below. It reads the key from the FINCHREACH_API_KEY environment variable through ${env:…}.
  4. Ask Cursor to list your LinkedIn accounts to check the connection.
.cursor/mcp.json
{
  "mcpServers": {
    "finchreach": {
      "url": "https://mcp.finchreach.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:FINCHREACH_API_KEY}"
      }
    }
  }
}

Replace lk_YOUR_KEY with your key. The step-by-step Cursor guide has every step, a test prompt and troubleshooting.

Common questions

No. With approval mode on, the default, every write Cursor makes through Finchreach (posts, comments, reactions, messages, invitations) becomes a pending action. You approve or reject it under Approvals before anything happens on LinkedIn.

Not through Finchreach today: posts are text only, there is no scheduling, and company pages and analytics aren’t supported. Writes happen when you approve them.

Any automation of a personal LinkedIn account carries some risk under LinkedIn’s User Agreement, and no tool can promise otherwise. Finchreach lowers it by keeping a person in the loop: nothing goes out until you approve it, and actions happen at your pace, not in bulk.

Third-party facts checked on against Cursor docs.