Write SEO blog post drafts with Zed
Writing blog post drafts in Zed with StoreSEO means asking the Agent Panel to choose a Shopify blog and run StoreSEO's blog writer, so a complete SEO post is saved as a draft for you to review and publish.
Last updated: October 2026
Set up Zed for StoreSEO
Skip this if Zed is already connected. The full guide, with the alternatives, is on the Zed page.
- 1
Add StoreSEO as a remote server
Open Settings, then AI, then MCP Servers and add a remote server, or add this to settings.json yourself. Leave out headers so Zed can sign you in.
JSON{ "context_servers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } } - 2
Sign in and check the dot
Because the entry has no Authorization header, Zed prompts you to authenticate. Pick your Shopify store and approve in the browser. In Settings, AI, MCP Servers a green dot next to storeseo means the server is active. Then ask this in the Agent Panel.
PromptUse StoreSEO to show me my store's SEO score breakdown.
How does this work in Zed?
You are in Zed with the Agent Panel open and StoreSEO showing a green dot under Settings, AI, MCP Servers. You type the brief: topic, keyword, length and whether to add a featured image. The agent calls storeseo_start, because every StoreSEO tool needs the conversation id it returns, and then storeseo_list_blogs, which lists each synced blog with its numeric id, title and article count. A blog that is not synced in the StoreSEO app is not listed, and an empty list means you sync in the app first.
Zed's own behavior shapes this job more than most. By default Zed asks before every tool action, reads included, so you will see a confirmation for storeseo_start, for storeseo_list_blogs and again for each poll of storeseo_get_blog_post_job. That is a lot of clicking for a job that runs for a few minutes, because the agent polls until the job is completed, failed or cancelled. Separately from Zed, StoreSEO tells the agent to name the credit cost and wait for your yes before storeseo_generate_blog_post, since writing a post spends AI Content Optimizer credit that grows with word count and a featured image. Those are two different questions, one from the client and one from the agent.
A sensible setup is to allow the read tools you trust with per-tool keys, such as mcp:storeseo:storeseo_list_blogs and mcp:storeseo:storeseo_get_blog_post_job, and leave storeseo_generate_blog_post on confirm so Zed still stops before it spends credit. When the job completes, ask the agent to read the draft's SEO record with storeseo_get_resource_seo using resource type article. The post stays in Shopify as a draft, and you publish it from Shopify admin; nothing is written into your project.
-
You: Write a 1,200 word draft on how to care for linen shirts in my News blog.
- storeseo_start read-only
- storeseo_list_blogs read-only
-
Zed: News is blog 1042. The post spends AI credit based on its length and is saved as a draft only. Shall I start writing it?
-
You: Yes, start writing.
- storeseo_generate_blog_post needs approval
- storeseo_get_blog_post_job read-only
-
Zed: The job is at step 2 of 5, so the draft is not finished. I will poll it again; Zed may ask you to allow each check.
What to ask Zed
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 first.
Write a StoreSEO blog draft targeting best gifts for coffee lovers, with a featured image, and check the job until it is completed.
Read the SEO record of the blog draft the last job created and list what to fix before I publish it.
- 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 Zed 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 Zed
Zed's default is to ask before every tool action, reads included, and this job polls storeseo_get_blog_post_job for a few minutes, so you can face a string of prompts. Allow only the read tools with per-tool keys such as mcp:storeseo:storeseo_get_blog_post_job and leave storeseo_generate_blog_post on confirm. If you set agent.tool_permissions.default to allow, Zed stops asking altogether, and then the cost confirmation StoreSEO asks the agent for in the panel is the only check before credit is spent, so use that setting sparingly.
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
Why does Zed keep asking me to confirm while the blog post is being written?
Zed asks before tool actions by default, and the agent polls storeseo_get_blog_post_job until the job finishes. Allow that read tool with a per-tool key and keep the generate tool on confirm.
Will Zed publish the post to my Shopify blog?
No. StoreSEO saves the post as a draft article in the blog you choose, and 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 Zed guides