How to connect Replit Agent to LinkedIn, step by step

What you need

• A Finchreach account (sign in at finchreach.com) and the LinkedIn account you want Replit Agent to work on.
• Replit Agent (transport and plan requirements aren’t stated. Traffic goes through Replit’s security scanner).
• 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 “Replit Agent”.
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 Replit Agent

1. Open the Integrations pane → MCP servers → + Add MCP server.
2. Enter a name and the HTTPS URL https://mcp.finchreach.com/mcp.
3. Under Advanced settings add a custom header: Authorization = Bearer lk_YOUR_KEY (or X-API-Key = lk_YOUR_KEY).
4. Click Test & save.

Arbitrary custom headers are supported (Replit’s own example is X-API-Key, which Finchreach accepts). OAuth with dynamic registration is detected automatically when a server offers it.

Requirements: Transport and plan requirements aren’t stated. Traffic goes through Replit’s security scanner.

Step 4: Test the connection

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

Troubleshooting

• If Test & save fails, check for a space or line break pasted with the 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 Replit Agent’s documentation, checked on 2026-10-28; client screens change often.

What to ask Replit Agent next

Ask your assistant“Use my LinkedIn profile to fill in the portfolio app you’re building.”

Ask your assistant“After the deploy, draft a LinkedIn post with the live link.”

Ask your assistant“Read my LinkedIn profile and draft a short bio for the app’s footer.”

More ideas on the Replit Agent integration page.

Common questions