FinchreachConnect your LinkedIn

Updated

Kimi Code logoMoonshot AI · Coding agentConnects directly

What can Kimi Code do on LinkedIn with Finchreach?

Kimi Code can read your LinkedIn feed, messages and notifications, search LinkedIn, and draft posts, comments, messages and connection invitations through Finchreach’s remote MCP server. Add the server to Kimi Code and sign in to Finchreach (OAuth) or use your Finchreach API key; every write waits in your approval queue until you approve it.

Connect your LinkedIn Read the docs

What can Kimi Code do on your LinkedIn?

Kimi Code already sits next to your code, commits and changelog. That makes it good at the LinkedIn jobs developers put off: writing about what you shipped, answering technical messages, and finding the people behind a library, all without leaving the terminal.

Ask your assistant“Read the diff of this release and draft a LinkedIn post for developers.”
Ask your assistant“Search LinkedIn for engineers who posted about Kimi models and summarize their opinions.”
Ask your assistant“Draft replies to my unread LinkedIn messages, short and friendly.”
Reads (run right away)Writes (wait for your approval)
linkedin_list_accounts: The LinkedIn accounts connected to your workspacelinkedin_create_post: A text post
linkedin_get_profile: A LinkedIn profilelinkedin_send_dm: A direct message
linkedin_get_feed: Your home feedlinkedin_send_invitation: A connection invitation, with an optional note
linkedin_get_notifications: Your notificationslinkedin_react_to_post: A reaction on a post (like by default)
linkedin_get_conversations: Your message threadslinkedin_unreact: Removes your reaction from a post
linkedin_get_messages: The messages in a threadlinkedin_comment_on_post: A comment on a post
linkedin_search: Search everything, posts, people or companieslinkedin_delete_comment: Deletes one of your comments
linkedin_get_received_invitations: Coming soon: the connection invitations waiting for your answerlinkedin_accept_invitation: Coming soon: accepts a received invitation
linkedin_get_action: The status of a write: waiting for approval, approved, rejected or done

What happens when Kimi Code drafts something?

  1. Kimi Code calls a write tool, for example linkedin_create_post with the text it wrote.
  2. Finchreach doesn’t post it. It stores a pending action and tells the assistant it is waiting for approval.
  3. You open Approvals, read the exact text and the account it would go out from, and approve or reject it.
  4. Approved actions run on LinkedIn; rejected ones never do. Kimi Code can check the outcome with linkedin_get_action.

Approval mode is on by default for every workspace. It is what makes it reasonable to let an assistant draft in your name.

Does Kimi Code work with Finchreach today?

Kimi Code
Remote MCP serversBuilt in
Finchreach (OAuth or API key)Connects directly
How sure we areHigh: from the official docs
Checked on2026-10-28

Headers are supported, or "bearerTokenEnvVar": "FINCHREACH_API_KEY" in place of headers to read the key from the environment. OAuth (/mcp-config login <name>) isn’t needed.

Finchreach’s server, https://mcp.finchreach.com/mcp, uses Streamable HTTP (pasting the bare https://mcp.finchreach.com works too). It signs in with OAuth 2.1, where you log in to Finchreach and approve a LinkedIn account and scopes, or with an API key sent as Authorization: Bearer lk_… or X-API-Key.

How do I connect Kimi Code?

  1. Create an API key under API keys and connect your LinkedIn account under Accounts.
  2. Edit ~/.kimi-code/mcp.json (or .kimi-code/mcp.json in the project) as below, or use /mcp-config in the TUI.
  3. With the legacy kimi-cli: kimi mcp add --transport http finchreach https://mcp.finchreach.com/mcp --header "Authorization: Bearer lk_YOUR_KEY".
  4. Ask Kimi Code to list your LinkedIn accounts to check the connection.
~/.kimi-code/mcp.json
{
  "mcpServers": {
    "finchreach": {
      "url": "https://mcp.finchreach.com/mcp",
      "headers": {
        "Authorization": "Bearer lk_YOUR_KEY"
      }
    }
  }
}

Replace lk_YOUR_KEY with your key. The step-by-step Kimi Code guide has every step, a test prompt and troubleshooting.

Common questions

No. With approval mode on, the default, every write Kimi Code makes through Finchreach (posts, comments, reactions, messages, invitations) becomes a pending action. You approve or reject it under Approvals before anything happens on LinkedIn.

Not through Finchreach today: posts are text only, there is no scheduling, and company pages and analytics aren’t supported. Writes happen when you approve them.

Any automation of a personal LinkedIn account carries some risk under LinkedIn’s User Agreement, and no tool can promise otherwise. Finchreach lowers it by keeping a person in the loop: nothing goes out until you approve it, and actions happen at your pace, not in bulk.

Third-party facts checked on against Kimi Code docs.