# What can Kimi Code do on LinkedIn with Finchreach?

Source: https://finchreach.com/integrations/kimi
Third-party facts checked on 2026-10-28.

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.

## 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 workspace | `linkedin_create_post`: A text post |
| `linkedin_get_profile`: A LinkedIn profile | `linkedin_send_dm`: A direct message |
| `linkedin_get_feed`: Your home feed | `linkedin_send_invitation`: A connection invitation, with an optional note |
| `linkedin_get_notifications`: Your notifications | `linkedin_react_to_post`: A reaction on a post (like by default) |
| `linkedin_get_conversations`: Your message threads | `linkedin_unreact`: Removes your reaction from a post |
| `linkedin_get_messages`: The messages in a thread | `linkedin_comment_on_post`: A comment on a post |
| `linkedin_search`: Search everything, posts, people or companies | `linkedin_delete_comment`: Deletes one of your comments |
| `linkedin_get_received_invitations`: Coming soon: the connection invitations waiting for your answer | `linkedin_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](https://finchreach.com/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 servers | Built in |
| Finchreach (OAuth or API key) | Connects directly |
| How sure we are | High: from the official docs |
| Checked on | 2026-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](https://finchreach.com/api-keys) and connect your LinkedIn account under [Accounts](https://finchreach.com/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:
```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](https://finchreach.com/guides/kimi) has every step, a test prompt and troubleshooting.

## Questions

### Can Kimi Code post on LinkedIn without me?

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](https://finchreach.com/approvals) before anything happens on LinkedIn.

### Can Kimi Code post images, schedule posts or manage a company page?

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.

### Is it safe for my LinkedIn account?

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.

## Sources

- [Kimi Code docs](https://moonshotai.github.io/kimi-code/en/customization/mcp)

## Related

- [Step-by-step: connect Kimi Code](https://finchreach.com/guides/kimi)
- [Get a daily LinkedIn feed digest with Kimi Code](https://finchreach.com/blog/kimi-linkedin-feed-digest)
- [All integrations](https://finchreach.com/integrations)