Updated

Lovable logoLovable · App builderConnects, with conditions

How to connect Lovable 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 Lovable with the header Authorization: Bearer lk_…. Test with a read, and approve the first draft under Approvals. One caveat: the tools work only in the build chat, not in published apps, and Lovable doesn’t document which header it sends.

What you need

  • A Finchreach account (sign in at finchreach.com) and the LinkedIn account you want Lovable to work on.
  • Lovable (all plans; admins can turn off custom MCP. Connections are personal).
  • 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 “Lovable”.
  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 Lovable

  1. Connectors → Add custom → MCP server → name and URL https://mcp.finchreach.com/mcp.
  2. Authentication: “Bearer token or API key”, then paste lk_YOUR_KEY.
  3. Use it in the build chat, for example to pull your LinkedIn profile into an about page.

OAuth is the default; Bearer token / API key and no auth are alternatives. Lovable doesn’t document which header the token goes in or the transport, so test it.

Requirements: All plans; admins can turn off custom MCP. Connections are personal.

Step 4: Test the connection

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

Troubleshooting

  • MCP tools work only in the chat while you build. A published Lovable app can’t call Finchreach through this connector.
  • If the connection fails, try the key with and without 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 Lovable’s documentation, checked on 2026-10-28; client screens change often.

What to ask Lovable next

Ask your assistant“Read my LinkedIn profile and use it to write the About section of my portfolio site.”
Ask your assistant“When the landing page is done, draft a LinkedIn post announcing it.”
Ask your assistant“Draft a LinkedIn post introducing the app with a link to the preview.”

More ideas on the Lovable 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. Lovable 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 “Lovable”) lets you revoke one without breaking the others.

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

Third-party facts checked on against Lovable docs.