What can Claude Code do on LinkedIn with Finchreach?
Claude Code 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 Claude Code and sign in to Finchreach (OAuth) or use your Finchreach API key; every write waits in your approval queue until you approve it.
What can Claude Code do on your LinkedIn?
Claude Code already sits next to your code, commits and changelog. That makes it good at the LinkedIn jobs developers put off: writing about what you shipped, answering technical messages, and finding the people behind a library, all without leaving the terminal.
Ask your assistant“Turn this week’s merged pull requests into a LinkedIn post draft about what we shipped.”
Ask your assistant“Read my unread LinkedIn messages and draft short replies to the ones from recruiters.”
Ask your assistant“Search LinkedIn for posts about MCP servers from the last week and summarize the main points.”
| Reads (run right away) | Writes (wait for your approval) |
|---|---|
linkedin_list_accounts: The LinkedIn accounts connected to your workspace | linkedin_create_post: A text post |
linkedin_get_profile: A LinkedIn profile | linkedin_send_dm: A direct message |
linkedin_get_feed: Your home feed | linkedin_send_invitation: A connection invitation, with an optional note |
linkedin_get_notifications: Your notifications | linkedin_react_to_post: A reaction on a post (like by default) |
linkedin_get_conversations: Your message threads | linkedin_unreact: Removes your reaction from a post |
linkedin_get_messages: The messages in a thread | linkedin_comment_on_post: A comment on a post |
linkedin_search: Search everything, posts, people or companies | linkedin_delete_comment: Deletes one of your comments |
linkedin_get_received_invitations: Coming soon: the connection invitations waiting for your answer | linkedin_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 Claude Code drafts something?
- Claude Code calls a write tool, for example
linkedin_create_postwith the text it wrote. - Finchreach doesn’t post it. It stores a pending action and tells the assistant it is waiting for approval.
- You open Approvals, read the exact text and the account it would go out from, and approve or reject it.
- Approved actions run on LinkedIn; rejected ones never do. Claude Code 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 Claude Code work with Finchreach today?
| Claude Code | |
|---|---|
| Remote MCP servers | Built in |
| Finchreach (OAuth or API key) | Connects directly |
| How sure we are | High: from the official docs |
| Checked on | 2026-10-28 |
Full custom-header support, with ${VAR} and ${VAR:-default} expansion, so the Finchreach key goes straight into Authorization: Bearer. Without the header, Claude Code can sign in with OAuth through /mcp, which Finchreach supports too.
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 Claude Code?
- Create an API key under API keys and connect your LinkedIn account under Accounts.
- Run
claude mcp add --transport http finchreach https://mcp.finchreach.com/mcp --header "Authorization: Bearer lk_YOUR_KEY". Add--scope projectto write a shared.mcp.jsonin the repo instead of your user config. - To keep the key out of the repo, use the
.mcp.jsonform below and setFINCHREACH_API_KEYin your shell: Claude Code fills in${VAR}in headers. - Ask Claude Code to list your LinkedIn accounts to check the connection.
claude mcp add --transport http finchreach https://mcp.finchreach.com/mcp \
--header "Authorization: Bearer lk_YOUR_KEY"Replace lk_YOUR_KEY with your key. The step-by-step Claude Code guide has every step, a test prompt and troubleshooting.
Common questions
No. With approval mode on, the default, every write Claude Code 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 Claude Code docs.
