WordPress 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 WordPress 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 write a WordPress article about it as a draft for review
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 WordPress
WordPress is a blog, not a social network, so Bolta has its own tool for it (create-wordpress-blog-post). It resolves the WordPress account, creates the draft and sets the article's settings in one call.
- Articles saved as a draft, with a title, excerpt, categories, tags and SEO meta.
- Featured and inline images, uploaded to the WordPress Media Library.
WordPress limits and format rules
Bolta's posting rules for your workspace (get-posting-rules) win if they differ from this page.
Not promised for WordPress from Kimi K3: Pages and custom post types. This page does not confirm them. Rankings. Bolta prepares an article for search and never promises a position.
| What to know | The destination's rule | What Bolta does |
|---|---|---|
| Title | Not stated on this page. | The title you set. If you do not set one, Bolta uses the first line of the post text. |
| Status | Not stated on this page. | WordPress has its own status field, which is separate. Bolta's own approval decides when the article goes out. |
| Several sites | Not stated on this page. | With more than one WordPress account, Bolta returns a list and asks which one to use. |
| Length | Not stated on this page. | No limit that Bolta checks. |
| Formatting | Not stated on this page. | Markdown is shown as formatting, so headings, lists and links work. |
Kimi K3 jobs for WordPress, and how to write them
- 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
- Name the site if you have more than one. Bolta asks when you do not.
Example prompts for WordPress
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 write a WordPress article about it as a draft for review
List my Bolta brands and the accounts connected to each
Turn docs/guide.md into a WordPress article with a title and meta description and show me the text
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 WordPress article in your brand voice (save-post). A saved draft is never public.
- 02
You read the exact text
On WordPress the exact text is the whole article, with its title, excerpt, tags, meta description and images, so read all of it.
- 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 WordPress
Parts of this route are not confirmed. The note above says which.
For WordPress, 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 WordPress account itself is connected inside Bolta, not in Kimi K3.
Kimi Code CLI is a terminal agent from Moonshot AI, so a WordPress 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.
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_.
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.
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.
- 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.
- 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.
- 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.
- 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.
- Setup: 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.
- 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.
- Bolta REST API from a Kimi shell command. The Bolta API is documented at /docs/api and a terminal agent can call it, but we have not tested that from Kimi Code.
- A routine you confirmed and switched on runs from Bolta on its own schedule.
- 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.
Connect Kimi K3 to Bolta
Kimi Code reads MCP servers from mcp.json. The generic MCP guide has the Bolta address and key steps.
WordPress questions, answered for Kimi K3
- Will Kimi K3 publish a WordPress article without asking me?
- No. Bolta saves the article as a draft. It can submit for review, schedule or publish, but only after you have seen the exact text and said yes.
- What does SERP-ready mean for an article from Kimi K3?
- It means Bolta prepared the article technically and editorially, with headings, a meta title and description, and the focus keyphrase placed sensibly. It does not promise a ranking.
- 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 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.
- 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.
- /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.
- Does Kimi K3 publish WordPress articles without my yes?
- No. Nothing is approved, scheduled or published until you say yes to that WordPress article. 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.
WordPress from other AI agents
The same WordPress limits apply whichever agent asks. The connection and the setup are what change.
Try a WordPress draft from Kimi K3
Connect Kimi K3, ask for a WordPress draft and read the exact text. Nothing goes live until you say yes.