Kimi K3 + Mastodon

Mastodon posts with Kimi K3 and Bolta

Turn changelogs and git history into social drafts from the Kimi Code terminal. Parts of the Kimi K3 route are not confirmed yet, and the note below says which. Nothing goes live on Mastodon until you say yes.

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

Kimi K3Bolta connected
You

Read the top entry in CHANGELOG.md and draft a Mastodon post about it inside my instance's limit

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.

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.
Bolta on Mastodon

What Bolta does on Mastodon

The text limit on Mastodon is set by your own instance, and Bolta reads it for the connected account instead of using one fixed number. The usual limit is 500 characters.

  • Text posts, within the limit your instance sets.
  • Public posts by default, or another visibility if you set it.
Limits and format

Mastodon limits and format rules

Bolta's posting rules for your workspace (get-posting-rules) win if they differ from this page.

Not promised for Mastodon from Kimi K3: Polls, threads and instance-specific features. None is confirmed for Bolta. Any rule from a particular instance. Each instance sets its own, so check yours.

Mastodon limits and format rules
What to knowMastodon's own ruleWhat Bolta does
Post lengthNot stated on this page.Set by your instance. Bolta reads it per account, and the usual limit is 500. Text over the limit is trimmed back to the last whole sentence or word that fits.
VisibilityNot stated on this page.Public unless you set another visibility.
FormattingNot stated on this page.Mastodon posts are plain text here. Markdown is flattened, and #hashtags and @mentions stay as typed.
Finding conversationsNot stated on this page.Hashtag-based. The query is folded into a single tag, because full-text status search is unavailable on most instances.
Best practices

Kimi K3 jobs for Mastodon, and how to write them

  • Keep one repo per brand by using a project-level .kimi-code/mcp.json
  • Check how recent posts performed, then draft the next one from that
  • Ask for your instance's limit before drafting. It differs from instance to instance.
Prompts

Example prompts for Mastodon

Things to type in Kimi K3. Each one asks for a draft and shows you the text first.

Read the top entry in CHANGELOG.md and draft a Mastodon post about it inside my instance's limit

What is waiting for my yes in Bolta?

Turn the release notes into a Mastodon post with one relevant hashtag and show it to me first

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

Review

Bolta saves a draft, you read the exact text, you say yes

  1. 01

    Bolta saves a draft

    Kimi K3 asks Bolta for the Mastodon post in your brand voice (save-post). A saved draft is never public.

  2. 02

    You read the exact text

    On Mastodon the exact text includes its visibility, because the default is public, and where the limit for your instance would cut it.

  3. 03

    You say yes

    Only then does Bolta schedule or publish (publish-post), in your workspace's timezone. Safe Mode, client sign-off and brand approval rules still apply.

Kimi K3 and Bolta

Using Kimi K3 for Mastodon

Parts of this route are not confirmed. The note above says which.

For Mastodon, Kimi K3, from Moonshot AI, reaches Bolta through Remote MCP server in mcp.json (Kimi Code CLI). Sign-in: Sign in (OAuth) or Bolta API key. The Mastodon account itself is connected inside Bolta, not in Kimi K3.

Kimi Code CLI is a terminal agent from Moonshot AI, so a Mastodon draft can start from your README, changelog or git log. The Kimi chat app is not covered here.

An illustration from the Kimi K3 guide, not real output. You ask: What is waiting for my yes in Bolta? The reply goes along these lines: 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.

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.

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.

The MCP connection works without it. Other agents on the same machine that read ~/.agents/skills can share the same copy.

  • 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.
  • 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.
  • 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.
  • 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.
  • Setup: 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.
  • Setup: 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.
  • Hosted MCP with browser sign-in. Kimi'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.
  • A post you approved and scheduled in Bolta publishes at its time without Kimi or your machine.
  • 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.
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.

FAQ

Mastodon questions, answered for Kimi K3

What is the Mastodon character limit for a post from Kimi K3?
It depends on your instance. Bolta reads the limit for the connected account, and the usual limit is 500 characters. Anything over it is trimmed back to the last whole sentence or word.
Are Mastodon posts from Kimi K3 public?
Yes, unless you set another visibility. Say who may see the post when you ask, and check it when you read the draft.
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.
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.
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.
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.
Does Kimi K3 publish Mastodon posts without my yes?
No. Nothing is approved, scheduled or published until you say yes to that Mastodon post. Whether Kimi K3 completes the connection is not fully confirmed, so read the note above first.

More from Kimi K3

Kimi K3 can work with the other networks Bolta publishes to. Each page has its own limits and review notes.

Mastodon from other AI agents

The same Mastodon limits apply whichever agent asks. The connection and the setup are what change.

Try a Mastodon draft from Kimi K3

Connect Kimi K3, ask for a Mastodon draft and read the exact text. Nothing goes live until you say yes.