ByteDance · Code editorUnverifiedWhat can Trae do on LinkedIn with Finchreach?
Probably, but it isn’t confirmed: Trae’s docs don’t confirm header support for remote servers; the mcp-remote bridge is the fallback. If it connects, Trae can read your LinkedIn feed, messages and notifications, search LinkedIn, and draft posts, comments, messages and connection invitations, with every write waiting for your approval. For a confirmed route, use Cursor or Cline.
What can Trae do on your LinkedIn?
Trae 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“Draft a LinkedIn post about the side project in this folder.”
Ask your assistant“Read my LinkedIn notifications and tell me who reacted to or commented on my posts.”
Ask your assistant“Search LinkedIn for frontend developers in Singapore and list ten profiles.”
| 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 Trae drafts something?
- Trae 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. Trae 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 Trae work with Finchreach today?
| Trae | |
|---|---|
| Remote MCP servers | Not confirmed |
| Finchreach (OAuth or API key) | Unverified |
| How sure we are | Low: little or no official documentation |
| Checked on | 2026-10-28 |
Trae probably supports remote servers with headers, but we couldn’t confirm it: its official MCP docs came back incomplete. The mcp-remote bridge works with any client that runs local stdio servers.
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 Trae?
- Create an API key under API keys and connect your LinkedIn account under Accounts.
- Open Settings → MCP → Add → Add Manually and paste the entry below.
- If the server doesn’t connect, replace it with the mcp-remote fallback (second snippet), which runs locally and sends the header itself. It needs Node.js.
- Ask Trae to list your LinkedIn accounts to check the connection.
{
"mcpServers": {
"finchreach": {
"url": "https://mcp.finchreach.com/mcp",
"headers": {
"Authorization": "Bearer lk_YOUR_KEY"
}
}
}
}Replace lk_YOUR_KEY with your key. The step-by-step Trae guide has every step, a test prompt and troubleshooting.
Common questions
No. With approval mode on, the default, every write Trae 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 Trae docs.