Facebook 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 Facebook 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.
Read the top entry in CHANGELOG.md and draft a Facebook post for our Page about it
Illustration of the reply: Bolta returns a draft showing the connected account and the scheduled time, with Approve, Edit and Reject actions.
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.
What Bolta does on Facebook
Bolta lists each Facebook Page as its own account, so you name the Page the post is for rather than a personal profile.
- Posts to a connected Facebook Page. Each Page is its own account in Bolta.
- Text, images, or one video. Media is optional.
Facebook limits and format rules
Network rules last checked 2026-07-28. Bolta's posting rules for your workspace (get-posting-rules) win if they differ from this page.
Not promised for Facebook from Kimi K3: Facebook Groups, Events, Stories and Reels. This page does not confirm that Bolta publishes them. A Facebook character limit. Bolta checks none, so this page gives no number.
| What to know | Facebook's own rule | What Bolta does |
|---|---|---|
| Text length | Not stated on this page. | Bolta does not check the length, so Facebook may refuse longer text. |
| Video and images | Not stated on this page. | One video per post, and a video cannot be mixed with images. |
| Several parts | Not stated on this page. | The first part is the post. Each other part is posted as a comment on it. |
| Pages and profiles | Every Page is administered through a personal account, but visitors see only the Page and not the people running it. | Posts go to Pages. Each Facebook Page is listed as its own account. |
| Search | Posts are ranked in Facebook search, and a public post can reach people you are not connected to, so the wording matters. | Bolta publishes the text you approved, in plain text. |
Kimi K3 jobs for Facebook, and how to write them
- Summarise this week's git log into an update for your build-in-public audience
- Check how recent posts performed, then draft the next one from that
- Name the Page. If you run several, ask for the account list first so the draft is saved against the right one.
Example prompts for Facebook
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 Facebook post for our Page about it
What is waiting for my yes in Bolta?
Turn the README intro into a Facebook post and show me the text before saving it
Which accounts can you post to, and how did last month go?
Bolta saves a draft, you read the exact text, you say yes
- 01
Bolta saves a draft
Kimi K3 asks Bolta for the Facebook post in your brand voice (save-post). A saved draft is never public.
- 02
You read the exact text
On Facebook the exact text includes which Page it is for, and any later parts that will be posted as comments.
- 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.
Using Kimi K3 for Facebook
Parts of this route are not confirmed. The note above says which.
For Facebook, 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 Facebook account itself is connected inside Bolta, not in Kimi K3.
Kimi Code CLI is a terminal agent from Moonshot AI, so a Facebook 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: Show me what the Friday release-notes routine did last week. The reply goes along these lines: 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.
Servers added mid-session only show in a new session, so close and reopen Kimi before you sign in.
If you keep one user-level entry for many brands, name the brand in every prompt and ask Kimi to list workspaces first.
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.
- 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.
- Results. Ask how last month's posts did on an account and draft the next one from the best performer. Reads only, nothing changes.
- 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.
- 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.
- Setup: 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.
- Setup: 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.
- Kimi chat app at kimi.com. We have not confirmed that the chat app accepts custom MCP servers. This page covers the terminal agent only.
- 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.
- 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.
Connect Kimi K3 to Bolta
Kimi Code reads MCP servers from mcp.json. The generic MCP guide has the Bolta address and key steps.
Facebook questions, answered for Kimi K3
- Does Kimi K3 post to my Facebook profile or my Page?
- To a Page. Bolta lists each Facebook Page as its own account, and the draft is saved against the Page you name. A Page is administered through a personal account, but visitors see only the Page.
- Can Kimi K3 attach a video and photos to the same Facebook post?
- No. Bolta allows one video per post and does not allow a video together with images. If you want both, make two posts.
- 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.
- 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.
- 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.
- 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.
- Does Kimi K3 publish Facebook posts without my yes?
- No. Nothing is approved, scheduled or published until you say yes to that Facebook 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.
Facebook from other AI agents
The same Facebook limits apply whichever agent asks. The connection and the setup are what change.
Try a Facebook draft from Kimi K3
Connect Kimi K3, ask for a Facebook draft and read the exact text. Nothing goes live until you say yes.