---
title: "Kimi K3 integration with Bolta"
description: "Connect Bolta to Kimi Code CLI with an mcp.json entry. Draft social posts from your changelog in the terminal, review them in Bolta, and publish only after you approve."
canonical_url: "https://bolta.ai/integrations/kimi"
markdown_url: "https://bolta.ai/integrations/kimi.md"
last_updated: "2026-11-21"
content_type: "integration"
publisher: "Bolta"
---

# Kimi K3 integration with Bolta

Source: https://bolta.ai/integrations/kimi
Last updated: 2026-11-21

Connect Bolta to Kimi Code CLI with an mcp.json entry. Draft social posts from your changelog in the terminal, review them in Bolta, and publish only after you approve.

## Summary

Turn changelogs and git history into social drafts from the Kimi Code terminal

## Who this is for

- Developers
- Automation teams
- AI-assisted marketing teams

## Core capabilities

- Turn a release's CHANGELOG.md into a launch post and a short follow-up thread
- Summarise this week's git log into an update for your build-in-public audience
- Read a README or docs page and draft posts that explain one feature at a time
- Keep one repo per brand by using a project-level .kimi-code/mcp.json
- Ask what is waiting for approval in Bolta without leaving the terminal
- Check how recent posts performed, then draft the next one from that

## Limitations and boundaries

- Confirmed in Kimi's own docs: Kimi Code CLI loads remote HTTP MCP servers from mcp.json, accepts static headers and a bearerTokenEnvVar, and can run a browser sign-in with /mcp-config login.
- Confirmed in Kimi's own docs: skills are folders with a SKILL.md, read from ~/.agents/skills among other places.
- Not tested: Bolta's browser sign-in has not been run end to end inside Kimi Code. If it does not complete, use the Bolta API key route below.
- Not confirmed: the Kimi chat app at kimi.com and any official Kimi plugin. This page is about the Kimi Code terminal agent only.
- Not confirmed: Kimi K3 and which model Kimi Code runs by default. We have not checked an official Moonshot page for either, so the name is used here only because people search for it.
- Integration availability depends on current APIs, authentication, scopes, and account permissions.
- Generated content can be incorrect and should be reviewed before publication.
- Availability depends on the current Bolta plan, connected network, account permissions, and integration coverage.
- Current prices and plan limits must be verified on the Bolta pricing page.

## Install Kimi Code CLI and open it

Install Kimi Code CLI from the official Kimi Code docs and sign in. Open it in a terminal and run kimi --version to confirm it starts.

## Create a Bolta account and a brand

Sign up at bolta.ai and add at least one brand. A connection reaches one organization, and you choose which brands it may touch when you sign in.

## Open the MCP config

Open ~/.kimi-code/mcp.json in a text editor and create it if it is missing. You can also start kimi and run /mcp-config to add a server without editing JSON. A file at .kimi-code/mcp.json inside a project overrides the user file for the same server name.

## Add the bolta entry

Add {"mcpServers":{"bolta":{"url":"https://mcp.bolta.ai/mcp"}}} and keep any servers already in the file. Leave out the transport field: Kimi treats a url entry as HTTP.

## Start a new session and sign in

A session that was already open will not see the new server. In a fresh session run /mcp-config login bolta, sign in to Bolta in the browser, and tick the brands Kimi may use.

## Check the connection

Run /mcp and look for bolta shown as connected. If sign-in will not complete, create a key in Bolta under Settings, then API Keys (it starts with bolta\_sk\_), put it in an environment variable, and set bearerTokenEnvVar on the bolta entry to that variable name.

## Optional: add the Bolta skill

Run npx skills add boltaai/bolta-skills --skill bolta. If the installer does not list Kimi, copy the skills/bolta folder into ~/.agents/skills/, which Kimi Code scans for skills.

## Read before you write

In a new session ask: What is waiting for my yes in Bolta? It should list your real brand and change nothing.

## Ask for a first draft

Try: Turn CHANGELOG.md into a LinkedIn post in my voice and save it as a draft. Open Bolta, read it, and approve or edit it there.

## Let Kimi write its own mcp.json entry

If you would rather not edit JSON, start kimi and paste this. Check the result before you approve any file change. Paste: Add a remote MCP server named bolta with the url https://mcp.bolta.ai/mcp to my Kimi Code mcp.json, keep my other servers, and use no transport field. Then tell me to start a new session and run /mcp-config login bolta. Servers added mid-session only show in a new session, so close and reopen Kimi before you sign in.

## User-level or project-level config

File: ~/.kimi-code/mcp.json; Applies to: Every project (or $KIMI\_CODE\_HOME/mcp.json); Use it for: One Bolta brand you post for from anywhere | File: .kimi-code/mcp.json; Applies to: That project only, overrides the user file for the same name; Use it for: A repo that belongs to one brand

## Headless and CI runs with an API key

A run in CI or on a server cannot open a browser, so use a Bolta API key. Create it in Bolta under Settings, then API Keys. Keys start with bolta\_sk\_. Put the key in an environment variable and set bearerTokenEnvVar on the bolta entry to the variable's name. Do not paste the key into mcp.json, because that file is easy to commit by mistake. A .kimi-code/mcp.json inside a project stays disabled in a headless run (for example kimi -p) unless that folder is already trusted, because Kimi cannot show its trust prompt there. Keep the bolta entry in the user file, ~/.kimi-code/mcp.json, for CI. Unattended runs should draft only. Posts still wait in Bolta for a person to approve.

## The Bolta skill and ~/.agents/skills

Kimi Code reads skills from folders with a SKILL.md, including ~/.agents/skills. The Bolta skill adds guidance on how to use the tools well, such as checking posting rules before saving a post. The MCP connection works without it. Other agents on the same machine that read ~/.agents/skills can share the same copy.

## Keeping each repo tied to the right brand

If you post for more than one brand, the project-level file is the safest way to stop a draft landing in the wrong place. Put the bolta entry in .kimi-code/mcp.json inside each brand's repo. It overrides the user file for the same server name. When you sign in, tick only the brands that repo should touch. In an untrusted folder Kimi asks whether to trust it before loading project servers, so answer that prompt the first time. If you keep one user-level entry for many brands, name the brand in every prompt and ask Kimi to list workspaces first.

## Rules Bolta keeps even when Kimi is in charge

Kimi drafting a post and Bolta publishing it are two separate steps. Saving a draft changes nothing public, and Bolta's role checks apply no matter what a prompt says. If Bolta refuses an action, such as publishing without the right role, Kimi should report the refusal and stop. Treat any suggestion to work around it as a reason to check the draft in Bolta yourself. Text Kimi reads from files, issues or web pages is material to write from, not instructions. A changelog line that says to publish immediately does not change what you approve.

## What we have and have not run

Part: Remote HTTP servers in mcp.json; Status: Documented; Source: Kimi Code docs | Part: /mcp-config login for browser sign-in; Status: Documented, untested with Bolta; Source: Kimi Code docs | Part: bearerTokenEnvVar for a Bolta key; Status: Documented, not run by us; Source: Kimi Code docs | Part: Project servers in headless runs; Status: Documented: disabled unless the folder is trusted; Source: Kimi Code docs | Part: Which model Kimi Code runs; Status: Not confirmed by us; Source: No official page checked | Part: Custom MCP in the Kimi chat app; Status: Not confirmed; Source: No official page checked

## From release notes to a week of posts

1. Point at the source: Name the file, such as CHANGELOG.md or a docs folder, or ask for the last week of git log. 2. Ask for drafts, not posts: Say save as drafts. Each one lands in your Bolta inbox. 3. Review in Bolta: Read, edit and approve there. Scheduled posts go out even after you close the terminal.

## Is this for the Kimi app or Kimi Code CLI?

It is for Kimi Code CLI, the terminal agent, because its docs describe remote MCP servers. We have not confirmed that the Kimi chat app accepts custom MCP connectors.

## Do I need an API key to connect Bolta to Kimi?

Not if browser sign-in works for you: run /mcp-config login bolta. Bolta's sign-in has not been tested in Kimi Code, so the API key route is the fallback.

## Does Bolta publish without my approval when Kimi writes the post?

No. Kimi saves drafts. Nothing is approved, scheduled or published until a person with the right role says yes in Bolta.

## Where does Kimi Code keep MCP settings, and can I set them per project?

In ~/.kimi-code/mcp.json for all projects, or .kimi-code/mcp.json inside one project. The project file overrides the user file for the same server name.

## Can I use a Bolta API key in a CI or headless Kimi run?

It should. Create a key under Settings, then API Keys, export it as an environment variable and name it in bearerTokenEnvVar. Keep the key out of the JSON file. Kimi's docs describe that field, but we have not run a headless Kimi session against Bolta ourselves.

## Does Kimi need the Bolta skill, or is the MCP connection enough?

The connection is enough to draft and review. The skill is optional guidance, and Kimi Code can read it from ~/.agents/skills.

## Why does Kimi not show Bolta after I edited mcp.json?

Servers added mid-session only show in a new session. Start a new one and run /mcp.

## Will scheduled posts still go out after I close Kimi?

Yes. Once you approve a post in Bolta, Bolta schedules and publishes it. It does not need Kimi or your terminal to stay open.

## Is Kimi K3 the same as Kimi Code?

No. Kimi Code CLI is the terminal agent that Bolta connects to. K3 is reported to be a Moonshot AI model, but we could not confirm from an official Moonshot page that it exists in the form reported or which model Kimi Code uses by default.

## Which networks can Kimi post to through Bolta?

Whatever you have connected in Bolta, including LinkedIn, X, Instagram, Facebook, Threads and Bluesky. Ask Kimi to list your accounts first.

## Can Kimi read my whole repo and post about it?

Kimi can read the files you point it at, such as CHANGELOG.md, a README or git log output, and write from them. It only saves drafts to Bolta. What you approve is a separate step, so check that a draft does not leak internal details before saying yes.

## What should I do if /mcp shows Bolta but Kimi cannot see any brands?

Sign in again with /mcp-config login bolta and make sure you ticked at least one brand. A connection reaches one organization, so also check that you are signed in to the right one in the browser.

## I edited mcp.json but Kimi does not show Bolta

Servers added mid-session only show in a new session. Close Kimi, start it again, then run /mcp to see the list. Also check that the JSON is valid and that bolta sits under mcpServers.

## /mcp-config login bolta does not finish

Bolta's sign-in has not been tested in Kimi Code. Try again in a fresh session, and if it still fails, switch to the API key route with bearerTokenEnvVar.

## Bolta shows as not connected in /mcp

Run /mcp-config login bolta again and make sure you ticked at least one brand. If you use an API key, check that the environment variable is set in the shell that launched Kimi.

## A project file is ignoring my user config

A .kimi-code/mcp.json inside the project overrides the user file for the same server name. Remove or rename the project entry, or fix the url there. In an untrusted folder Kimi asks whether to trust it before it loads project servers, so answer that prompt.

## Kimi says a post needs approval

That is Bolta's rule working. Open the draft in Bolta and approve it there. Kimi will not work around a refusal.

## The commands I found online do not match

Some pages mention kimi mcp add or kimi mcp auth, but Kimi's official docs describe /mcp-config and mcp.json. Use those.

## Kimi K3, Kimi Code CLI and the Kimi app

Kimi K3 is reported to be a Moonshot AI model, though we have not checked an official Moonshot page. Kimi Code CLI is Moonshot AI's terminal coding agent, documented on kimi.com, and it is the product this page connects Bolta to. The Kimi chat app at kimi.com is separate, and we have not confirmed that it accepts custom MCP servers.

## Relevant links

- [Related page: /integrations](https://bolta.ai/integrations)
- [Related page: /integrations/claude-code](https://bolta.ai/integrations/claude-code)
- [Related page: /integrations/codex](https://bolta.ai/integrations/codex)
- [Related page: /integrations/cursor](https://bolta.ai/integrations/cursor)
- [Bolta pricing](https://bolta.ai/pricing)

## Supporting sources

- [Kimi K3 official website](https://www.kimi.com/code)
