Write SEO blog post drafts with Kiro
Writing blog post drafts in Kiro with StoreSEO means asking Kiro's agent to pick a Shopify blog and run StoreSEO's blog writer, so a finished SEO post is saved as a draft you review and publish yourself.
Last updated: October 2026
Set up Kiro for StoreSEO
Skip this if Kiro is already connected. The full guide, with the alternatives, is on the Kiro page.
- 1
Add StoreSEO to your Kiro MCP config
Open the Command Palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows and Linux), search for MCP and open the workspace config (.kiro/settings/mcp.json) or the user config (~/.kiro/settings/mcp.json). Paste this and save. Kiro applies the change on save, and the first connection opens a browser sign-in: pick your Shopify store and approve.
JSON{ "mcpServers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } }
How does this work in Kiro?
You are in the Kiro IDE with StoreSEO defined in your MCP configuration, either in the workspace file .kiro/settings/mcp.json or in the user file. You describe the post in the agent chat: topic, keyword, length and whether it needs a featured image. Kiro calls storeseo_start first, since every StoreSEO tool needs the conversation id it returns, and then storeseo_list_blogs, which returns each synced blog's numeric id, title and article count. Only blogs synced in the StoreSEO app appear, so an empty list sends you to the app.
Two kinds of confirmation meet in this job. Kiro asks before it runs a tool unless the tool is in the autoApprove list for the server, and StoreSEO separately tells the agent to state the credit cost and wait for your yes before it writes. Writing a post spends AI Content Optimizer credit that grows with the word count and a featured image, so the second confirmation matters. After your yes, Kiro calls storeseo_generate_blog_post and then polls storeseo_get_blog_post_job with the job id. The run takes a few minutes, and the poll reports steps completed out of total until the status is completed, failed or cancelled. When it is done you can ask Kiro to read the draft with storeseo_get_resource_seo using resource type article.
The practical configuration for this job is to put the quiet tools in autoApprove, for example storeseo_start, storeseo_list_blogs and storeseo_get_blog_post_job, so the polling does not interrupt you, and to leave storeseo_generate_blog_post out so Kiro still shows its own prompt before credit is spent. The draft stays in Shopify; you open it there, edit it and publish it. Nothing is added to your workspace files.
-
You: Write a 1,200 word draft on how to care for linen shirts in the News blog.
- storeseo_start read-only
- storeseo_list_blogs read-only
-
Kiro: News is blog 1042. The post spends AI credit based on its length and is saved as a draft, not published. Do you want me to write it?
-
You: Yes, write it.
- storeseo_generate_blog_post needs approval
- storeseo_get_blog_post_job read-only
-
Kiro: The job is at step 3 of 5 and still running, so the draft is not finished. I will check again and tell you when it is completed.
What to ask Kiro
Use StoreSEO to list my blogs and write a 1,200 word draft on how to care for linen shirts in the News blog. Tell me the credit cost and wait for my yes.
Write a StoreSEO blog draft targeting best gifts for coffee lovers with a featured image, and keep checking the job until it completes.
Check the SEO record of the draft you created and tell me which issues to fix before I publish it from Shopify admin.
- List my blogs and write a 1,200 word draft on how to care for linen shirts in the News blog. Tell me the cost first.
- Write a draft post targeting best gifts for coffee lovers, with a featured image.
- How far along is the blog post you started?
- Check the SEO score of the draft you just wrote.
- Draft three post ideas for my store and write the strongest one.
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 Kiro 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 Kiro
Keep storeseo_generate_blog_post out of autoApprove. That list tells Kiro to run a tool without asking, and a wildcard would run every StoreSEO tool, so the only prompt left before credit is spent would be the confirmation StoreSEO asks the agent for. List the individual read tools instead: storeseo_start, storeseo_list_blogs and storeseo_get_blog_post_job. Also check which file defines storeseo, because a workspace .kiro/settings/mcp.json overrides a user-level entry with the same name, and a different sign-in could point the draft at another store.
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
Which StoreSEO tools should I put in Kiro's autoApprove for blog posts?
The read tools: storeseo_start, storeseo_list_blogs and storeseo_get_blog_post_job. Leave storeseo_generate_blog_post out so Kiro still asks before credit is spent.
Does Kiro publish the post it writes?
No. StoreSEO saves the generated post as a draft article in the Shopify blog you pick. You publish it from Shopify admin.
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 Kiro guides