How to connect Devin to LinkedIn, step by step

What you need

• A Finchreach account (sign in at finchreach.com) and the LinkedIn account you want Devin to work on.
• Devin (you need the “Manage MCP Servers” permission).
• 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 “Devin”.
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 Devin

1. Open Customize → MCPs → Add MCP → Add custom MCP. (Older UI: Settings → MCP Marketplace → Add Your Own.)
2. Transport: HTTP. Server URL: https://mcp.finchreach.com/mcp.
3. Authentication: Auth Header. The header name defaults to Authorization; enter Bearer lk_YOUR_KEY as the value.
4. Save, then click Test tools.

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

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

Devin offers None, Auth Header and OAuth, at organization or personal scope.

Requirements: You need the “Manage MCP Servers” permission.

Step 4: Test the connection

In Devin, 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. Devin can check the result with linkedin_get_action: pending, approved, rejected, executed, failed or expired.

Troubleshooting

• Add it at personal scope if the LinkedIn account is yours alone; organization scope gives every member’s sessions the same key.
• 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 Devin’s documentation, checked on 2026-10-28; client screens change often.

What to ask Devin next

Ask your assistant“When you open the release PR, also draft a LinkedIn post announcing it.”

Ask your assistant“Draft a LinkedIn message to the open-source maintainer whose bug we fixed upstream.”

Ask your assistant“Summarize LinkedIn posts about our product from this week.”

More ideas on the Devin integration page.

Common questions