Updated

Le Chat logoMistral AI · Chat assistantConnects directly

How to connect Le Chat to LinkedIn, step by step

Create an API key at finchreach.com/api-keys, connect LinkedIn at finchreach.com/accounts, then add https://mcp.finchreach.com/mcp to Le Chat with the header Authorization: Bearer lk_…. Test with a read, and approve the first draft under Approvals.

What you need

  • A Finchreach account (sign in at finchreach.com) and the LinkedIn account you want Le Chat to work on.
  • Le Chat (only an admin can add connectors (on Free, Pro and Student, the account owner is the admin)).
  • 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 “Le Chat”.
  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 Le Chat

  1. Open Connectors → + Add Connector → Custom MCP Connector.
  2. Enter a name without spaces (finchreach), the URL https://mcp.finchreach.com/mcp and a short description, then click Connect.
  3. Le Chat detects the authentication method and asks for a token: choose HTTP Bearer Token and paste lk_YOUR_KEY.
  4. Turn the connector on in a chat and ask for something on LinkedIn.
Le Chat connector
Name:  finchreach
URL:   https://mcp.finchreach.com/mcp
Auth:  HTTP Bearer Token = lk_YOUR_KEY

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

Le Chat supports None, Bearer or Basic (sent in Authorization) and OAuth 2.1, so the Finchreach key works as a Bearer token. Streamable HTTP over valid TLS, which Finchreach uses.

Requirements: Only an admin can add connectors (on Free, Pro and Student, the account owner is the admin).

Step 4: Test the connection

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

Troubleshooting

  • Names can’t contain spaces. Paste the key alone: Le Chat adds Bearer .
  • 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 Le Chat’s documentation, checked on 2026-10-28; client screens change often.

What to ask Le Chat next

Ask your assistant“Draft a LinkedIn post in English and French about our new office in Paris.”
Ask your assistant“Read my LinkedIn messages from this week and tell me which ones are sales pitches.”
Ask your assistant“Search LinkedIn for AI startups in Europe that posted about hiring this month.”

More ideas on the Le Chat integration page.

Common questions

No, a key is shown only once. Create a new one under API keys, put it in your config, and revoke the old one.

No. Le Chat only gets your Finchreach API key. Your LinkedIn connection stays in Finchreach, and you can revoke the key at any time without touching LinkedIn.

Yes, but one key per tool (for example one named “Le Chat”) lets you revoke one without breaking the others.

Revoke its key under API keys; Le Chat gets a 401 from then on. Then remove the server from its config.

Third-party facts checked on against Le Chat docs.