How to connect Trae to LinkedIn, step by step

What you need

• A Finchreach account (sign in at finchreach.com) and the LinkedIn account you want Trae to work on.
• Trae.
• About five minutes.

Step 1: Create a Finchreach API key

1. Sign in at finchreach.com and open API keys.
2. Create a key and name it after the tool, for example “Trae”.
3. Copy it right away: it starts with lk_ and is shown only once.

Step 2: Connect your LinkedIn account

1. Open Accounts and click to connect LinkedIn.
2. Follow the steps until the account shows as connected.

Approval mode is on by default: nothing the assistant drafts reaches LinkedIn until you approve it.

Step 3: Add Finchreach to Trae

Not confirmed: 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.

1. Open Settings → MCP → Add → Add Manually and paste the entry below.
2. 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.
3. Project-level .trae/mcp.json reportedly needs “Enable Project MCP” turned on (third-party report).

{
  "mcpServers": {
    "finchreach": {
      "url": "https://mcp.finchreach.com/mcp",
      "headers": {
        "Authorization": "Bearer lk_YOUR_KEY"
      }
    }
  }
}

{
  "mcpServers": {
    "finchreach": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.finchreach.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer lk_YOUR_KEY"
      }
    }
  }
}

Replace lk_YOUR_KEY with your key. Keep the key out of shared files and repos; where Trae can read it from an environment variable, prefer that.

Step 4: Test the connection

In Trae, start with a read. It runs right away and proves the key and the account work:

Ask your assistant“List my connected LinkedIn accounts, then summarize my five latest notifications.”

You should see calls to linkedin_list_accounts and linkedin_get_notifications. Then try a write, which goes to your approval queue instead of LinkedIn:

Ask your assistant“Draft a short LinkedIn post saying I’m trying a new AI assistant workflow. Submit it for my approval.”

Step 5: Approve or reject it in Finchreach

1. Open Approvals. The draft is there with its exact text and the account it would go out from.
2. Approve it to publish, or reject it (reject the test post if you don’t want it live).
3. Trae can check the result with linkedin_get_action: pending, approved, rejected, executed, failed or expired.

Troubleshooting

• If the remote entry fails, use the mcp-remote fallback.
• 401 or “unauthorized”: the key is wrong, revoked or missing its prefix. Finchreach accepts Authorization: Bearer lk_… or X-API-Key: lk_…; check for a missing Bearer , quotes or a trailing space.
• A tool is missing: the key’s permissions don’t include it. Create a key with the permissions you need under API keys.
• “No LinkedIn account”: connect one under Accounts, or reconnect it if its session expired.
• A post or message “didn’t go out”: it is probably still waiting under Approvals. Writes run only after you approve them.

Still stuck? Compare your setup with Trae’s documentation, checked on 2026-10-28; client screens change often.

What to ask Trae next

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.”

More ideas on the Trae integration page.

Common questions