Updated

v0 logoVercel · App builderConnects directly

How to connect v0 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 v0 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 v0 to work on.
  • v0 (plan requirements aren’t stated).
  • 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 “v0”.
  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 v0

  1. In the prompt form, open + → MCPs → add a custom server with the URL https://mcp.finchreach.com/mcp.
  2. Authentication: Bearer Token, value lk_YOUR_KEY. (Custom Headers, OAuth and No Auth are the other options.)
  3. Through the API: create the server with POST /v1/mcp-servers (below), then pass its id in mcpServerIds when you create a chat.
POST /v1/mcp-servers
{
  "name": "finchreach",
  "url": "https://mcp.finchreach.com/mcp",
  "auth": {
    "type": "bearer",
    "token": "lk_YOUR_KEY"
  }
}
Alternative auth
{
  "auth": {
    "type": "custom-headers",
    "headers": {
      "Authorization": "Bearer lk_YOUR_KEY"
    }
  }
}

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

Bearer tokens and custom headers (up to 10) are both supported; the server must be HTTPS.

Requirements: Plan requirements aren’t stated.

Step 4: Test the connection

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

Troubleshooting

  • MCP tools are used during generation only: the app v0 builds doesn’t call Finchreach at runtime.
  • 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 v0’s documentation, checked on 2026-10-28; client screens change often.

What to ask v0 next

Ask your assistant“Build a personal landing page using my LinkedIn headline and experience.”
Ask your assistant“Use my LinkedIn headline to write the hero line of the page.”
Ask your assistant“Draft a LinkedIn post announcing the site once it’s generated.”

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

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

Third-party facts checked on against v0 docs, v0.app.