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

Schedule social media posts with Kimi K3

Kimi Code is Moonshot AI's terminal coding agent, and it can load remote MCP servers from a small mcp.json file. Add Bolta's hosted server at https://mcp.bolta.ai/mcp and Kimi can write posts in your brand voice and save them as drafts that wait in Bolta for your yes.

  • Point Kimi Code at CHANGELOG.md, a README or git log and get post drafts in your voice
  • Setup is one mcp.json entry and one slash command, or a Bolta API key for headless runs
  • Drafts wait in Bolta after the terminal closes, and nothing goes out until you approve

Nothing is approved, scheduled or published until you say yes.

Partly confirmed, see what is and is notChecked 2026-11-21

Kimi Code reads MCP servers from mcp.json. The generic MCP guide has the Bolta address and key steps.

Kimi K3Bolta connected
You

Read CHANGELOG.md and save a LinkedIn draft about the newest release

Illustration of the reply: Bolta returns a draft showing the connected account and the scheduled time, with Approve, Edit and Reject actions.

Illustration. Your drafts show your real text, account and time.
Two steps

Add Bolta to Kimi Code, then ask for a draft

  1. 01

    Add the server and sign in

    Add a bolta entry with the url https://mcp.bolta.ai/mcp to your mcp.json, open a new Kimi session, run /mcp-config login bolta and tick the brands Kimi may use.

  2. 02

    Ask what is waiting for you

    Type: What is waiting for my yes in Bolta? Kimi should name your real brand and change nothing. Then ask for your first draft.

What is and is not confirmed

Read this before you set up Kimi K3

  • 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.
Behind the prompt

What happens when Kimi Code works with Bolta

Kimi Code is a terminal agent, so the loop starts from files on your disk and ends in Bolta's review screen. Each step below names the Bolta tool Kimi would call.

  1. 01

    Find the brand and its accounts

    Kimi asks Bolta which organizations and brands your sign-in covers, then which social accounts hang off the brand you picked.

    list-workspaces

  2. 02

    Check what is connected

    Before drafting for a network, Kimi lists the accounts so it does not write an X post for a brand that only has LinkedIn.

    list-accounts

  3. 03

    Read your voice

    Kimi pulls the brand's voice context so a changelog entry reads like your company wrote it, not like release-note boilerplate.

    get-voice-context

  4. 04

    Check the posting rules

    Bolta returns the length and format limits for the chosen network, which matters when a long CHANGELOG.md is the source.

    get-posting-rules

  5. 05

    Save the draft

    Kimi writes the text from the file or git log you pointed at and saves it as a draft. Saving does not approve, schedule or publish anything.

    save-post

  6. 06

    You review in Bolta

    The draft appears in your Bolta inbox. You read it, edit it and say yes there, or reject it with a reason.

    list-inbox-items

Setup

Set up Kimi K3

Connect once. Everything below works from Kimi K3 afterwards.

  1. 01

    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.

  2. 02

    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.

  3. 03

    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.

  4. 04

    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.

  5. 05

    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.

  6. 06

    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.

  7. 07

    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.

  8. 08

    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.

  9. 09

    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.

Connect

Connect Kimi K3 to Bolta

Kimi Code reads MCP servers from mcp.json. The generic MCP guide has the Bolta address and key steps.

Connection routes

Which Bolta connection methods work with Kimi Code

Status reflects what Kimi's own docs say plus what we have actually run. Nobody at Bolta has completed the browser sign-in inside Kimi Code yet.

Which Bolta connection methods work with Kimi Code
MethodWith Kimi K3How
Hosted MCP with browser sign-inNot confirmedKimi's docs describe /mcp-config login for remote servers, so it should work with https://mcp.bolta.ai/mcp. We have not run it end to end.
Hosted MCP with a Bolta API keyNot confirmedKimi's docs allow static headers and a bearerTokenEnvVar on a url entry, and Bolta accepts a key on its hosted server, so it should work. We have not run it from Kimi Code. Create the key under Settings, then API Keys, and name the environment variable that holds it.
Skill via npx skills addNot confirmedKimi scans ~/.agents/skills for SKILL.md folders. We have not checked whether the installer lists Kimi, so copy skills/bolta into that folder if it does not.
Plugin or extensionNot availableBolta has no Kimi plugin. Kimi's docs mention a Plugins page for packaging skills, but we did not verify it.
Kimi chat app at kimi.comNot confirmedWe have not confirmed that the chat app accepts custom MCP servers. This page covers the terminal agent only.
Bolta REST API from a Kimi shell commandNot confirmedThe Bolta API is documented at /docs/api and a terminal agent can call it, but we have not tested that from Kimi Code.
Capabilities

What you can run in Bolta from Kimi K3

Each row is an area of Bolta, with the real tools behind it.

  • Posts from your repo

    Point Kimi at CHANGELOG.md, a README or recent git history and it saves drafts per network. Several drafts at once go in as a batch, still unapproved.

    save-postbulk-create-postsget-posting-rules

  • Review and approval

    Ask what is waiting, then approve, reject or send a post to a teammate. Direct approval needs your yes for that exact post, and Bolta's own role checks still apply.

    list-inbox-itemsapprove-many-postsreject-postsubmit-for-review

  • Weekly routines

    Describe a cadence such as one release-notes post every Friday. Kimi shows the plan, you confirm it, and it is saved switched off until you turn it on separately.

    planconfirm-plancreate-routineactivate-routine

  • Launch campaigns

    For a bigger release, Kimi can plan a short campaign around one source such as a docs page, so the launch posts are drafted together.

    plan-campaigncreate-content-campaignanalyze-content-campaign-source

  • Voice and brand

    Kimi reads the voice profile and Business DNA before it writes, and can update them when you say how your tone has changed.

    get-voice-contextvoice-generateupdate-business-dna

  • Results

    Ask how last month's posts did on an account and draft the next one from the best performer. Reads only, nothing changes.

    get-account-analyticslist-account-insights

  • Replies and comments

    For Reddit, Threads, Bluesky and Mastodon, once a monitoring campaign is attached to the account in Bolta, Kimi can look for conversations about your release and draft a reply. Publishing a reply is a separate step that needs your yes.

    search-engagement-opportunitiesdraft-engagement-replypublish-engagement-reply

In practice

A sample release-day session in Kimi Code

A made-up example of the kind of exchange to expect. Wording, counts and results are illustrative.

IllustrationNot real output
  1. You

    Read CHANGELOG.md. We shipped 2.4.0 today. Draft a LinkedIn post and a shorter X post in our voice, and just save them.

  2. Tool call
    list-accounts

    Checks which networks this brand has connected

  3. Kimi K3

    This brand has LinkedIn and X connected. I will draft for both. Anything in 2.4.0 you do not want mentioned?

  4. You

    Skip the internal refactor. Lead with the new export option.

  5. Tool call
    get-voice-context

    Reads the brand voice before writing

  6. Tool call
    get-posting-rules

    Checks length limits for LinkedIn and X

  7. Tool call
    save-post

    Saves two drafts, unapproved and unscheduled

  8. Kimi K3

    Both drafts are saved in Bolta. Neither is approved or scheduled. The X post is the shorter one and leads with the export option. Open them in your inbox to edit.

  9. You

    The LinkedIn one is too long. Can you cut it to under 120 words?

  10. Tool call
    save-post

    Saves the shorter LinkedIn text as a new draft, still unapproved

  11. Kimi K3

    I trimmed it and saved the new version as a draft. Review both in Bolta. When you are happy, approve there and tell me the time you want.

Which sign-in

Browser sign-in or an API key

Both reach the same Bolta tools. The difference is who is at the keyboard.

Browser sign-in

Choose this when you are working at your own machine.

Run /mcp-config login bolta, approve in the browser and tick the brands. No secret sits in a file. This is the route we expect to work, but it has not been tested end to end in Kimi Code.

Bolta API key

Choose this for CI, a server or any run with no browser.

Create a key in Bolta under Settings, then API Keys. Export it as an environment variable and name that variable in bearerTokenEnvVar on the bolta entry, so the key never sits in the JSON.

Use cases

What can Kimi K3 do with Bolta?

  • 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
The connection

What is the Bolta MCP?

The server Kimi K3 talks to when it works with Bolta.

MCP, the Model Context Protocol, is the open standard that lets an AI app call tools in another product. Bolta runs a hosted MCP server at https://mcp.bolta.ai/mcp. Your AI app discovers its 67 tools and calls them for you: list your brands, save a draft, plan a routine, read results.

One connection is one organization. You tick the brands the app may reach, and every call is checked against your role, so the app can never do more in Bolta than you can. Approving, scheduling and publishing need your yes.

  • Brands & accounts6 tools

    The brands this connection reaches, who works on them and who can approve, their approval settings, connected social accounts, and each platform's posting rules.

    list-workspaces, list-workspace-members, set-brand-approval, list-accounts, get-connect-link, get-posting-rules

  • Posts9 tools

    Save a draft or edit a post with save-post, then publish it now or at a time with publish-post after the user says yes.

    list-workspace-posts, get-post, save-post, publish-post, delete-post, bulk-create-posts, create-wordpress-blog-post, list-recently-deleted, restore-deleted

  • Review4 tools

    Everything waiting for a yes: submit drafts to the team or send them to a named person for approval, approve one or many, reject with a reason, and work the inbox of routine and campaign drafts.

    list-inbox-items, submit-for-review, approve-many-posts, reject-post

  • Plans6 tools

    Have Bolta plan a routine or a campaign the way its own chat does, change it, then save it on the user's yes.

    plan, plan-routine, plan-campaign, recommend-routines, revise-plan, confirm-plan

  • Routines10 tools

    Work that repeats and runs in Bolta even with the app closed.

    list-routine-templates, list-routines, get-routine, create-routine, update-routine, activate-routine, pause-routine, archive-routine, run-routine-now, list-routine-runs

  • Campaigns6 tools

    One to four weeks of posts about one thing: a launch, an event, a season.

    list-content-campaigns, get-content-campaign, create-content-campaign, update-content-campaign, analyze-content-campaign-source, set-content-campaign-status

  • Team versions4 tools

    One idea written as one post per person on the team, each in their own voice.

    plan-team-posts, update-team-post-plan, generate-team-post-drafts, get-team-post-plan

  • Voice & business8 tools

    The brand's voice and business facts, and writing in that voice.

    get-voice-context, get-voice-profile, create-voice-profile, update-voice-profile, list-business-dna, extract-business-dna, update-business-dna, voice-generate

  • Suggestions2 tools

    What Bolta suggests changing, for a routine or the whole brand, from what people approved, edited and rejected.

    list-suggestions, decide-suggestion

  • Replies10 tools

    Find conversations worth joining, draft replies in the brand voice, and send them once the user says yes.

    search-engagement-opportunities, list-engagements, get-social-content, draft-engagement-reply, draft-inbound-reply, publish-engagement-reply, reply-to-social-content, react-to-social-content, send-outreach-reply, update-outreach-reply

  • Results2 tools

    How posts and accounts are performing.

    list-account-insights, get-account-analytics

Try it

Seven things to ask Kimi Code once Bolta is connected

Replies below are illustrative, not real output.

You in Kimi K3

Read CHANGELOG.md and save a LinkedIn draft about the newest release.

Bolta

I read the 2.4.0 section and wrote a 140-word draft in your voice. I saved it to Bolta and have not scheduled it. Open it in your Bolta inbox to review.

Draft saved. Waits for your yes.

save-post

You in Kimi K3

What is waiting for my yes in Bolta?

Bolta

Three items are waiting: two post drafts and one reply. Nothing has been approved or sent. Want me to read the drafts back to you?

Read only. Nothing changes.

list-inbox-items

You in Kimi K3

Plan a weekly release-notes routine from our repo for LinkedIn.

Bolta

Here is the plan: every Friday, draft one post from that week's changes, and send it to review. Nothing is saved yet. Say yes and I will confirm the plan, switched off until you turn it on.

Plan shown. Waits for your yes.

plan, confirm-plan, create-routine

You in Kimi K3

Which accounts can you post to, and how did last month go?

Bolta

You have LinkedIn and Bluesky connected for this brand. I pulled last month's analytics for each and can draft the next post from the best performer.

Read only. Nothing changes.

list-accounts, get-account-analytics

You in Kimi K3

Use git log for the last 7 days and draft three posts for X.

Bolta

I grouped the week's commits into three themes and saved three short drafts. None are approved or scheduled. The third is the weakest, so I flagged it for you to edit or drop.

Drafts saved. Wait for your yes.

get-posting-rules, bulk-create-posts

You in Kimi K3

Check the pending LinkedIn draft against our voice and tell me what to change.

Bolta

I read your brand's voice context and the draft waiting in your inbox. Two sentences are stiffer than your usual tone, and I suggest shorter versions. I have not edited or approved anything.

Read only. Nothing changes.

list-inbox-items, get-voice-context

You in Kimi K3

Show me what the Friday release-notes routine did last week.

Bolta

I pulled its recent runs. I can tell you whether each run drafted a post and where it went for review. I have not changed the routine.

Read only. Nothing changes.

list-routines, list-routine-runs

Bolta publishes to

  • LinkedIn
  • X
  • Instagram
  • Facebook
  • Threads
  • Bluesky
When the terminal closes

What keeps running when Kimi Code is closed

Kimi Code only works while a session is running. Bolta holds everything you saved, so closing the terminal loses nothing.

  • Drafts Kimi saved stay in your Bolta inbox until someone reviews them.
  • A post you approved and scheduled in Bolta publishes at its time without Kimi or your machine.
  • A routine you confirmed and switched on runs from Bolta on its own schedule.
  • A headless run such as kimi -p with an API key can save drafts from a CI job. Keep the bolta entry in the user-level file, because a project file stays disabled there until the folder is trusted.

What still needs Kimi open: writing new posts from your files, since Kimi is the one reading the repo. Unattended runs should draft only. Review and approval stay with a person in Bolta.

Fastest start

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.

Config location

User-level or project-level config

User-level or project-level config
FileApplies toUse it for
~/.kimi-code/mcp.jsonEvery project (or $KIMI_CODE_HOME/mcp.json)One Bolta brand you post for from anywhere
.kimi-code/mcp.jsonThat project only, overrides the user file for the same nameA repo that belongs to one brand
No browser

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.

Optional

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.

Agencies and monorepos

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.
Safety in the terminal

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.

Before you rely on it

What we have and have not run

What we have and have not run
PartStatusSource
Remote HTTP servers in mcp.jsonDocumentedKimi Code docs
/mcp-config login for browser sign-inDocumented, untested with BoltaKimi Code docs
bearerTokenEnvVar for a Bolta keyDocumented, not run by usKimi Code docs
Project servers in headless runsDocumented: disabled unless the folder is trustedKimi Code docs
Which model Kimi Code runsNot confirmed by usNo official page checked
Custom MCP in the Kimi chat appNot confirmedNo official page checked
Workflow

From release notes to a week of posts

  1. 01

    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. 02

    Ask for drafts, not posts

    Say save as drafts. Each one lands in your Bolta inbox.

  3. 03

    Review in Bolta

    Read, edit and approve there. Scheduled posts go out even after you close the terminal.

Safety

What Kimi K3 cannot do without you

Kimi K3 connects as: Remote MCP server in mcp.json (Kimi Code CLI).

  • Drafts are free, finals need your yes

    Kimi K3 can write, edit and save drafts at any time. Approving, scheduling, publishing, sending a reply, activating a routine or campaign and deleting each wait for your yes, shown against the exact text.

  • One connection, one organization

    When you connect Kimi K3 you tick the brands it may reach. It reaches only those, and when that is more than one brand, every call names the brand it is for.

  • Your role is the ceiling

    Each call Kimi K3 makes is checked like a normal request from you. Owners and admins can act on any post, creators on Bolta's drafts and on posts they are a named reviewer on, and viewers never approve or publish.

Terms

The words behind Kimi K3 and Bolta

For Kimi K3: Remote MCP server in mcp.json (Kimi Code CLI), signing in with Sign in (OAuth) or Bolta API key.

MCP
The Model Context Protocol, an open standard that lets an AI app call tools in another product. Bolta's hosted server is at https://mcp.bolta.ai/mcp, and Kimi K3 reaches Bolta through a connection like it.
Skill
A folder of instructions an AI app reads so it knows how to use Bolta well. It does not connect by itself: install it with npx skills add boltaai/bolta-skills --skill bolta next to the connection.
Plugin
A bundle that brings the connection and the skill in one install, where the app supports plugins. Claude Code has one, added with its plugin marketplace commands.
API key
A bolta_sk_ key you create in Settings, sent as a Bearer header. It carries the permissions you choose, which suits apps you configure by hand or anything that runs unattended.
Read the MCP docs

Setup for Kimi K3 is only partly confirmed. See what is and is not confirmed. Last checked 2026-11-21.

Same name, different products

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.

FAQ

Frequently asked questions

Short answers about using Kimi K3 with Bolta.

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.
Troubleshooting

If something does not work

Quick fixes for the common snags.

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.

Ready to schedule social media posts with Kimi K3?

Connect Kimi K3 and ask for your first draft. Nothing goes out until you say yes.