Set up structured data with OpenCode
Setting up structured data with OpenCode means asking the open-source terminal agent to check which StoreSEO JSON-LD schema types are on and to send complete organization, product or review settings once you approve.
Last updated: October 2026
Set up OpenCode for StoreSEO
Skip this if OpenCode is already connected. The full guide, with the alternatives, is on the OpenCode page.
- 1
Add StoreSEO to OpenCode
Run this from the project that should use StoreSEO, or add --global to make it available in every project. OpenCode writes a remote server entry to its configuration; the equivalent hand-written entry is shown in the next step.
Terminalopencode mcp add storeseo --url https://mcp.storeseo.com/mcp
- 2
Sign in to your store
Remote servers use OAuth by default. Run the auth command, then pick your Shopify store in the browser and approve access. Inside OpenCode, /mcps does the same: select storeseo and sign in. opencode mcp list should then show it as connected.
Terminalopencode mcp auth storeseo opencode mcp list
How does this work in OpenCode?
You run OpenCode in a project folder and ask which schema types your store has enabled. The model sees StoreSEO tools named with the server prefix, such as storeseo_storeseo_list_schema_types, and it calls storeseo_start first, then the list tool. The terminal shows each call and the answer is a plain summary: which types are on, which are off and which accept settings. OAuth is on by default, so the sign-in you did with opencode mcp auth storeseo is stored by OpenCode, not in your project files.
For a configurable type the agent calls storeseo_get_schema_settings and receives the current settings plus the field template. This is where a terminal helps: you can keep your business details in a file in the repository, such as a short JSON or Markdown note, and tell OpenCode to build the settings object from it. It shows you the complete object, and after your yes calls storeseo_update_schema_settings. Remember that the update replaces the stored settings, so an object missing the logo drops the logo. Organization and local business share their business information, so keep the two consistent.
If you want a hard stop on the write, OpenCode lets you add a permission rule with a pattern that matches the tool name and denies it. That turns the session into a safe audit of your schema while you still use the same connection. Lift the rule when you are ready to apply, then ask again.
-
You: Which JSON-LD types are on for my store?
- storeseo_start read-only
- storeseo_list_schema_types read-only
-
OpenCode: Product schema is on. Organization is off. I can read its field template and build the settings from business.md. Shall I read it?
-
You: Yes, read it.
- storeseo_get_schema_settings read-only
-
OpenCode: The template matches business.md except the logo URL. Send the complete organization settings with the status on?
What to ask OpenCode
Use StoreSEO to list the JSON-LD schema types for my store and show which are enabled. Read only.
Read the organization schema settings, then fill the field template from business.md in this folder and show me the object before sending.
Check whether review schema can be enabled. Tell me what it depends on, then ask before changing anything.
- Which JSON-LD schema types are enabled on my store?
- Set up organization schema with my business name, logo and contact email. Read the current settings first.
- Turn on product schema and review schema.
- Is local business schema configured? Show me what is missing.
- Enable FAQ schema for products if my plan includes it.
What StoreSEO does: structured data (json-ld)
StoreSEO adds JSON-LD schema to your storefront so search engines and AI assistants can read your products, business and FAQs as data. The agent lists every schema type, reads a type's settings and its field template, and sends back a complete settings object.
Requires: The FAQ schema types need the FAQ Schema feature in your plan.
- 1
List the schema types
The agent lists every type with whether it is on and whether it takes settings. Configurable types are product, review, sale dates, product merchant, organization and local business.
- 2
Read before writing
For a configurable type it reads the current settings and the field template, because an update replaces the whole settings object rather than merging into it.
- 3
Fill in your details
Business name, address, contact details and similar fields come from you. Organization and local business share the same business information, so changing one changes both.
- 4
Switch it on
After your yes the agent sends the complete settings with the status. Organization, local business and product merchant need complete settings to be enabled.
Structured data (JSON-LD) reference
| Configurable types | Product, review, sale dates, product merchant, organization, local business |
|---|---|
| Toggle-only types | Every other type, including the four FAQ types |
| Update behaviour | Settings replace the stored object; read first, then send the full object |
| Dependencies | Review, sale dates and product merchant need product schema on; disabling product also disables product merchant |
| Shared data | Organization and local business share basic business information |
| FAQ types | Product, collection, article and page FAQ need the FAQ Schema feature in your plan |
| Sale dates | Also needs a discount permission that only the app's own Sale Dates toggle can request |
Rules OpenCode follows
- The agent reads the current settings before every settings update, because the update replaces them wholesale.
- Business details come from you; the agent does not invent an address, phone number or opening hours.
- Turning a schema type on or off changes your live storefront markup, so the agent confirms the change first.
- When a type is refused for a missing plan feature or dependency, the agent says which one rather than retrying.
In OpenCode
OpenCode V2 expects servers under mcp.servers, while older versions put the server directly under mcp, so check the layout your installed version documents before editing the config. OpenCode's docs describe deny rules for MCP tools but no ask-first mode, so the confirmation StoreSEO asks the agent for in the terminal is your main check on a schema update unless you deny the update tool by name. Tool names reach the model as server_tool, which is why a pattern such as storeseo_* can hide or deny tools without disconnecting the server. There is also no remove command, so delete the entry from the config and run opencode mcp logout storeseo to clear the sign-in.
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
How do I stop OpenCode from changing my schema settings?
Add a permission rule that denies the storeseo_update_schema_settings tool by name. The list and get tools keep working, so you can audit your schema types without the agent being able to write.
Can OpenCode build schema settings from a file in my project?
Yes. Point it at a note with your business details and ask it to fill the field template from storeseo_get_schema_settings. Check the full object it shows before you approve the update.
What schema types can StoreSEO add to my store?
StoreSEO manages product, review, sale dates, product merchant, organization and local business schema with settings, plus toggle-only types such as the FAQ types for products, collections, articles and pages.
Why does the agent read my schema settings before changing them?
A settings update replaces the whole stored object instead of merging. Reading first and sending back the complete object is the only way to change one field without wiping the others.
Why was review schema refused?
Review, sale dates and product merchant schema depend on product schema. Turn product schema on first, then enable the dependent type.
Do I need a particular plan for FAQ schema?
Yes. The four FAQ schema types need the FAQ Schema feature in your StoreSEO plan. Without it, any change to them is refused with a message saying the feature is not in your plan.
Keep going
Structured data (JSON-LD) with other agents
More OpenCode guides