What can Perplexity do on LinkedIn with Finchreach?
Perplexity can read your LinkedIn feed, messages and notifications, search LinkedIn, and draft posts, comments, messages and connection invitations through Finchreach, with one condition: Perplexity doesn’t document which header its API Key option uses, so test it. On the Mac, the mcp-remote bridge sends the header itself. Reads run right away; every write waits in your approval queue until you approve it.
What can Perplexity do on your LinkedIn?
Perplexity is where many people already think out loud. With Finchreach, LinkedIn joins that conversation: ask what happened in your notifications, have it draft a post or a reply in your voice, and decide later in Finchreach what actually goes out.
Ask your assistant“Research this company, then find its head of marketing on LinkedIn and draft a connection note.”
Ask your assistant“Summarize the LinkedIn posts I was tagged in this week.”
Ask your assistant“Draft a LinkedIn post that sums up this report, with the key number first.”
| 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 Perplexity drafts something?
- Perplexity 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. Perplexity 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 Perplexity work with Finchreach today?
| Perplexity | |
|---|---|
| Remote MCP servers | Built in |
| Finchreach (OAuth or API key) | Connects, with conditions |
| How sure we are | Medium: official docs incomplete, partly third-party sources |
| Checked on | 2026-10-28 |
Perplexity offers None, API Key and OAuth 2.0 for remote connectors, but doesn’t document which header the API key is sent in. If it isn’t Authorization: Bearer or X-API-Key, Finchreach will refuse it: test it, and on the Mac fall back to the local mcp-remote connector, which sends the header itself.
Requirements: Pro, Max or Enterprise, according to third-party sources.
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 Perplexity?
- Create an API key under API keys and connect your LinkedIn account under Accounts.
- Open Plugins in the sidebar (or Customize → Connectors) → Add custom → Add MCP connector → Remote.
- Name it Finchreach, enter the URL
https://mcp.finchreach.com/mcp, choose Authentication “API Key” and transport “Streamable HTTP”. - Ask Perplexity to list your LinkedIn accounts to check the connection.
npx -y mcp-remote https://mcp.finchreach.com/mcp --header "Authorization: Bearer lk_YOUR_KEY"Replace lk_YOUR_KEY with your key. The step-by-step Perplexity guide has every step, a test prompt and troubleshooting.
Common questions
No. With approval mode on, the default, every write Perplexity 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 Perplexity docs.
