OpenClaw (open source) · Autonomous agentConnects directlyWhat can OpenClaw do on LinkedIn with Finchreach?
OpenClaw 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 OpenClaw 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 OpenClaw do on your LinkedIn?
OpenClaw works through multi-step jobs on its own. LinkedIn becomes one step of them: research a list, read a profile, draft the note. The approval queue is the checkpoint where a person decides what goes out in your name.
Ask your assistant“When I ask from WhatsApp, check my LinkedIn messages from clients and draft replies.”
Ask your assistant“Draft a LinkedIn post from what I worked on this week.”
Ask your assistant“Find the people I’ve emailed this week on LinkedIn and draft an invitation with a note to each.”
| 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 OpenClaw drafts something?
- OpenClaw 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. OpenClaw 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 OpenClaw work with Finchreach today?
| OpenClaw | |
|---|---|
| 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 |
Headers are supported. They are ignored if auth: "oauth" is set, so leave auth out.
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 OpenClaw?
- Create an API key under API keys and connect your LinkedIn account under Accounts.
- Upgrade to OpenClaw 2026.5.12 or later (earlier versions could leak headers on cross-origin redirects, CVE-2026-53840).
- Open Settings → MCP (config editor) and add the entry below, or run
openclaw mcp set finchreach '<json>'.openclaw mcp add --url …has no header flag. - Ask OpenClaw to list your LinkedIn accounts to check the connection.
{
"mcp": {
"servers": {
"finchreach": {
"url": "https://mcp.finchreach.com/mcp",
"transport": "streamable-http",
"headers": {
"Authorization": "Bearer ${FINCHREACH_API_KEY}"
}
}
}
}
}Replace lk_YOUR_KEY with your key. The step-by-step OpenClaw guide has every step, a test prompt and troubleshooting.
Common questions
No. With approval mode on, the default, every write OpenClaw 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 OpenClaw docs, docs.openclaw.ai.