Write SEO blog post drafts with Kimi Code
Drafting blog posts in Kimi Code means asking Moonshot AI's terminal agent to have StoreSEO write an SEO-optimized article into one of your Shopify blogs as a draft, following the background job until it finishes and checking the draft.
Last updated: October 2026
Set up Kimi Code for StoreSEO
Skip this if Kimi Code is already connected. The full guide, with the alternatives, is on the Kimi Code page.
- 1
Add StoreSEO to Kimi Code
Create or edit ~/.kimi-code/mcp.json so every project on your machine can use StoreSEO. For one repository only, use .kimi-code/mcp.json inside it. You can also run /mcp-config in Kimi Code and have it add the server for you.
json config{ "mcpServers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } } - 2
Sign in to your store
Start a new Kimi Code session (a server added mid-session registers in the next one), run this command, then follow the browser window: pick your Shopify store and approve access.
new message to Kimi Code/mcp-config login storeseo
Step-by-step guide in the docs: How to connect StoreSEO MCP to Kimi Code
How does this work in Kimi Code?
You describe the post in the kimi prompt: a topic, who it is for and a rough length. Kimi Code calls storeseo_list_blogs to find the numeric blog id, because only blogs synced with StoreSEO appear, and an empty list means you sync in the app first. It then agrees the brief with you, including the word count and whether to add a featured image, since credit use grows with both. StoreSEO writes the article itself on its own servers, so the text is not the Kimi model's.
The write is storeseo_generate_blog_post, and it saves a draft article in the blog you chose. Nothing is published live; you review and publish from Shopify admin. The job runs for a few minutes in the background, so Kimi Code polls storeseo_get_blog_post_job and reports steps completed out of steps total until the status is completed, failed or cancelled. The draft row exists from the start, so a good agent does not call the article finished while the job is still running.
When the job completes, the agent reads the draft with storeseo_get_resource_seo using resource type article and the Shopify article id from the job result, and reports the score and anything still missing. A terminal helps with planning. Ask Kimi Code to scan your theme or content folder for product handles, then include them in the brief as internal link targets, or to keep a posts-plan.md file of topics so a series stays consistent without repeating titles.
-
You: Write a post on caring for linen shirts for my News blog.
- storeseo_start read-only
- storeseo_list_blogs read-only
-
Kimi Code: I found the News blog. A 1,200 word post with a featured image spends AI Content Optimizer credit, more than a shorter post without one, and it is saved as a draft only. Should I start the job?
-
You: Yes, start it with the image.
- storeseo_generate_blog_post needs approval
- storeseo_get_blog_post_job read-only
-
Kimi Code: Illustrative progress: 3 of 5 steps are complete, so the draft is not finished yet. I will check again shortly.
What to ask Kimi Code
Tap a prompt to copy it, then paste it into Kimi Code.
What StoreSEO does: blog post drafts
StoreSEO writes a full blog post with AI and saves it as a draft article in the Shopify blog you choose, optionally with a featured image. Nothing is published: you review and publish from Shopify admin.
Requires: Spends AI Content Optimizer credit; the cost grows with word count and a featured image. Blogs must be synced in the StoreSEO app.
- 1
Pick the blog
The agent lists your synced blogs, the sections posts go into, with their ids. An empty list means the blogs need syncing in the StoreSEO app first.
- 2
Agree the brief and cost
Topic, keyword, length and whether to add a featured image. The cost grows with length and the image, so the agent tells you and waits for your yes.
- 3
Generate in the background
Writing takes a few minutes. The agent polls the job and reports progress, and does not present the post as finished while it runs.
- 4
Check the draft
When the job completes, the agent can read the draft article's SEO record. You review and publish the post from Shopify admin.
Blog post drafts reference
| Output | A draft article in the chosen Shopify blog, never published live |
|---|---|
| Featured image | Optional; uploaded with the draft and adds to the cost |
| Run time | A few minutes in the background |
| Insufficient credit | The call fails before anything is queued or spent |
| Blogs | Only blogs synced with StoreSEO are listed; syncing is done in the app |
| Failed runs | The job reports the error and credits are settled automatically |
Rules Kimi Code follows
- The agent states the expected credit use and waits for your yes before it starts a post.
- Posts are saved as drafts only; publishing is done by you in Shopify admin.
- While the job runs, the agent reports progress and never presents the draft as finished.
In Kimi Code
Polling is where a terminal session can mislead you. Kimi Code may stop after a poll that shows the job still running, and the draft article already exists in Shopify at that point with partial content. Ask the agent to keep checking storeseo_get_blog_post_job until a terminal status, and open the draft only after it reports completed. If the job fails, StoreSEO settles the credits automatically, so do not start a second job before reading the error.
What runs without asking. Reads such as SEO scores, store listings, settings and Google reports run straight away. Generating a preview spends AI credit but writes nothing, and StoreSEO tells the agent to say what a generation will cost before it runs one. Applying content, optimizing images, changing settings, publishing llms.txt or agents.md, writing a product description and deleting anything wait for your yes in the conversation. That yes is an instruction the agent follows, not a lock on the server, so your client's own tool-approval setting is the hard stop.
Questions
Will Kimi Code publish the blog post it writes?
No. StoreSEO saves the article as a draft in your Shopify blog and nothing goes live from this job. You review the draft and publish it yourself in Shopify admin when you are ready.
Why does Kimi Code say I have no blogs to write into?
Only blogs synced with StoreSEO are listed, so an empty result means you need to sync your blogs in the StoreSEO app. No tool in the MCP server can sync them for you.
Will the agent publish a blog post on my store?
No. StoreSEO saves generated posts as drafts in the Shopify blog you choose. You review and publish them from Shopify admin.
How long does a blog post take?
A few minutes. The writing runs in the background and the agent checks the job until it is completed, failed or cancelled.
What does a blog post cost?
It spends AI Content Optimizer credit, and the amount grows with the word count and with a featured image. If you do not have enough credit the call fails before anything is spent.
Why does the agent say I have no blogs?
Only blogs synced with StoreSEO are listed. Sync your blogs in the StoreSEO app, then ask again.
Keep going
Blog post drafts with other agents
More Kimi Code guides