How to connect Kiro to LinkedIn, step by step

What you need

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

1. Turn on MCP in Kiro’s Settings.
2. Command palette: “Kiro: Open workspace MCP config (JSON)” (.kiro/settings/mcp.json) or the user config (~/.kiro/settings/mcp.json).
3. Paste the entry below. Add FINCHREACH_API_KEY to the “Mcp Approved Env Vars” setting and set it to lk_YOUR_KEY. Changes apply on save.

{
  "mcpServers": {
    "finchreach": {
      "url": "https://mcp.finchreach.com/mcp",
      "headers": {
        "Authorization": "Bearer ${FINCHREACH_API_KEY}"
      }
    }
  }
}

Headers and OAuth are supported; Finchreach uses the header.

Step 4: Test the connection

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

Troubleshooting

• ${FINCHREACH_API_KEY} stays empty (and the server returns 401) unless the variable is listed in “Mcp Approved Env Vars”.
• 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 Kiro’s documentation, checked on 2026-10-28; client screens change often.

What to ask Kiro next

Ask your assistant“Turn this spec into a short LinkedIn post about the feature we’re building.”

Ask your assistant“Draft a LinkedIn message to the hiring manager I met at the meetup, based on their profile.”

Ask your assistant“Summarize the LinkedIn posts in my feed about AWS this week.”

More ideas on the Kiro integration page.

Common questions