K llms.txt and agents.md

Publish llms.txt and agents.md with Kiro

Publishing llms.txt and agents.md with Kiro means asking AWS's agentic IDE to read your store's AI discovery file status through StoreSEO and to generate or switch files, while you decide which tools Kiro may run without asking.

Jump to the prompts Connect Kiro

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 working in Kiro, often on a theme or storefront project, and you ask whether the store serves a current llms.txt and a custom agents.md. Kiro calls storeseo_start, storeseo_get_llms_txt_status and storeseo_get_agents_md_status. The answer names the saved generation settings, the active version and its age, whether a rebuild is due, and whether /agents.md is custom or Shopify's default. If you listed those read tools in autoApprove in your mcp.json, they run without a prompt, which makes a status check quick.

Kiro's configuration is where this job gets safer or looser. autoApprove takes tool names, and disabledTools hides tools from the agent. A sensible setup for AI discovery files lists the read tools in autoApprove, namely storeseo_get_llms_txt_status, storeseo_get_agents_md_status and storeseo_list_llms_txt_versions, and leaves storeseo_generate_llms_txt, storeseo_generate_agents_md, storeseo_activate_llms_txt_version, storeseo_delete_llms_txt_version and storeseo_reset_agents_md out. StoreSEO tells the agent to name the live theme write, the publish and the credit cost before any of them and to wait for your yes. Kiro's own prompt then sits on top of that.

After a generation you can keep working in the same project. Ask Kiro to compare the llms.txt template in the theme with the active version, to write the returned agents.md text into a spec or docs file so the team can review what AI shopping agents are being told, or to list versions and pick an older one to activate. A rollback of llms.txt republishes a stored version, but deleting a version and resetting agents.md cannot be undone, so confirm those individually.

Kiro + StoreSEO Illustrative session

You: Check my llms.txt and agents.md, and rebuild whichever is out of date.
storeseo_start read-only
storeseo_get_llms_txt_status read-only
storeseo_get_agents_md_status read-only
Kiro: agents.md is custom and current. llms.txt needs a rebuild, and generating it writes to your live theme and Shopify Files. Rebuild llms.txt?
You: Yes, rebuild it.
storeseo_generate_llms_txt needs approval
Kiro: The rebuild is running. I will check the status until it finishes and tell you which version is live.

What to ask Kiro

Prompt 1

Use StoreSEO to check my llms.txt and agents.md status and list any llms.txt versions. Read only.

Prompt 2

Generate a new agents.md and save the returned text into docs/agents-md.md. Tell me the credit cost and that it goes live first.

Prompt 3

Activate the previous llms.txt version. Name the version and wait for my yes.

Is my llms.txt up to date, and which version is live right now?
Generate a new llms.txt that includes products and collections but not blog posts. Warn me before it goes live.
Show me my llms.txt versions and switch back to the one from last week.
Does my store serve a custom agents.md or Shopify's default?
Write an agents.md for my store and publish it. Tell me what it costs first.
Reset agents.md to Shopify's default.

What StoreSEO does: llms.txt and agents.md

llms.txt is a curated map of your store for AI crawlers, and agents.md tells AI shopping agents who you are and how to buy. StoreSEO generates both from your store data and publishes them to your live theme; the agent checks status, generates, switches llms.txt versions and resets agents.md to Shopify's default.

Requires: agents.md generation spends AI Content Optimizer credit and needs at least one published product.

1

Check what is live

The agent reads the llms.txt status (settings, latest version, whether a rebuild is due, public URL) and the agents.md status (custom file or Shopify's default, public URL).
2

Warn before publishing

Generating llms.txt writes a template to your live theme and uploads a copy to Shopify Files in the same run, with no separate publish step. Generating agents.md publishes it live at once and spends credit. The agent says so and waits for your yes.
3

Generate and wait

llms.txt generation takes a minute or two; the agent polls the status until it finishes. agents.md returns the published text and its URL straight away.
4

Manage versions

StoreSEO keeps the latest ten llms.txt versions. The live file serves the active version, which is not always the newest, and any version can be made active again.
5

Roll back

Deleting a version is permanent. Resetting agents.md drops the custom file so Shopify's default serves again, and there is no history to restore it from.

storeseo_get_llms_txt_statusstoreseo_generate_llms_txtstoreseo_list_llms_txt_versionsstoreseo_activate_llms_txt_versionstoreseo_delete_llms_txt_versionstoreseo_get_agents_md_statusstoreseo_generate_agents_mdstoreseo_reset_agents_md

llms.txt and agents.md reference

llms.txt	Generated from your products, collections, pages and posts; served at your store's /llms.txt
Where it is written	A template in the live theme plus a copy in Shopify Files, in the same run
Schedule	llms.txt can regenerate on a saved schedule; settings passed with a run are saved for scheduled runs
Versions kept	The latest ten; the live file serves the active one
Generation time	About one to two minutes for llms.txt
agents.md	AI-written from your brand profile, top products, collections and contact details; served at /agents.md
agents.md publish	Live immediately; replaces Shopify's native default
agents.md reset	Shopify's default serves again within seconds; the custom text is gone for good

Rules Kiro follows

The agent tells you that llms.txt generation writes to your live theme before it starts.
agents.md generation publishes live and spends credit, so the agent says both and waits for your yes.
Deleting an llms.txt version and resetting agents.md cannot be undone; the agent confirms each one.
Deleting the active llms.txt version promotes the next newest automatically, so the agent says which version will go live.

In Kiro

A wildcard in autoApprove would let Kiro run every StoreSEO tool without asking, including the ones that write to your live theme, publish agents.md and delete llms.txt versions. List individual read tools instead. Kiro's default behavior when autoApprove is empty is not described on its MCP configuration page, so check what your Kiro does before you rely on it. Also remember that a workspace .kiro/settings/mcp.json overrides a user-level entry with the same name, which can point the job at a different store than you expect.

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 llms.txt?

The read tools: storeseo_start, storeseo_get_llms_txt_status, storeseo_get_agents_md_status and storeseo_list_llms_txt_versions. Leave generate, activate, delete and reset out so Kiro prompts before they run.

Does Kiro wait for llms.txt generation to finish?

The agent polls storeseo_get_llms_txt_status after storeseo_generate_llms_txt until generation_ongoing is false, which takes about a minute or two. You can keep working in the project while it does.

What is the difference between llms.txt and agents.md?

llms.txt is a curated map of your store for AI crawlers and answer engines, served at /llms.txt. agents.md is the file AI shopping agents read to understand your brand and how to shop with you, served at /agents.md. StoreSEO can generate both.

Does generating llms.txt change my theme?

Yes. The same run writes an llms.txt template into your live theme and uploads a copy to Shopify Files. There is no separate publish step, which is why the agent should warn you before it starts.

Can I go back to an older llms.txt?

Yes. StoreSEO keeps the latest ten versions, and any of them can be made the active one, which republishes it to your storefront. Deleting a version is permanent.

Can I undo a generated agents.md?

You can reset it, which makes Shopify's native default serve again within seconds. The custom text is discarded with no history, so keep a copy if you might want it back.