Set up structured data with Cursor
Setting up structured data in Cursor means asking the editor's agent to list your Shopify store's JSON-LD types through StoreSEO, read a type's settings and send them back, while Cursor's tool cap and run modes decide whether the schema tools are available at all.
Last updated: October 2026
Set up Cursor for StoreSEO
Skip this if Cursor is already connected. The full guide, with the alternatives, is on the Cursor page.
- 1
Add StoreSEO to mcp.json
Put this in ~/.cursor/mcp.json to use StoreSEO in every project, or in .cursor/mcp.json inside one theme project. In the StoreSEO app's setup guide the same JSON goes into Settings, Tools and MCP, New MCP server.
JSON{ "mcpServers": { "storeseo": { "url": "https://mcp.storeseo.com/mcp" } } } - 2
Sign in to your store
Open Cursor's MCP settings (the Customize page in current versions), find storeseo and sign in when Cursor asks. A browser window opens: pick your Shopify store and approve access.
PromptUse StoreSEO to show me my store's SEO score breakdown.
- 3
Switch off four StoreSEO tools
StoreSEO has 44 tools and Cursor stops at about 40 active ones across all servers. In the storeseo entry in Cursor's MCP settings, turn off at least four you do not need. The four rank and competitor lookups are a good first choice if you are not on Pro.
Promptstoreseo_list_rank_locations storeseo_list_rank_languages storeseo_add_competitors storeseo_delete_competitor
How does this work in Cursor?
You have the theme project open in Cursor and ask the agent in the chat panel which schema types StoreSEO has enabled. It calls storeseo_start and storeseo_list_schema_types, and each call appears inline in the chat. By default Cursor asks before it runs an MCP tool, so on the first use you approve the call in the panel, and the result comes back as a plain list of types with their state.
The step that catches people here comes before any of that. StoreSEO exposes 44 tools and Cursor allows about 40 active tools across all your servers, so you have switched at least four off in MCP settings. If storeseo_get_schema_settings or storeseo_update_schema_settings was one of the ones you disabled, the agent will tell you it has no such tool, or quietly fall back to describing what it would do. Open the StoreSEO entry in Cursor's MCP settings and check that the three schema tools are enabled before you start; they are few enough to keep on while you drop tools for jobs you do not use.
Being in an editor gives you an advantage. The agent can open your theme files beside the StoreSEO results, find ld+json blocks that already exist and point at lines that would duplicate what StoreSEO outputs. When you ask it to set up organization schema, it reads the current settings and field template first, asks you for anything missing, and only after your yes calls the update with the complete object. You can then review the theme diff and the schema change in one sitting.
-
You: What schema is on in StoreSEO, and does this theme duplicate any of it?
- storeseo_start read-only
- storeseo_list_schema_types read-only
- storeseo_get_schema_settings read-only
-
Cursor: Product and review schema are on. Organization is off, and the theme has no Organization block. Do you want me to save your business details and switch organization schema on?
-
You: Yes, use the name and email from the footer.
- storeseo_update_schema_settings needs approval
What to ask Cursor
Use StoreSEO to list my JSON-LD schema types and tell me which ones are on. If a schema tool is unavailable, say which one.
Read my product merchant schema settings, show me the field template, and tell me what I need to fill in before it can be enabled.
Search this theme for ld+json blocks, then use StoreSEO to check whether organization schema is already on so we do not publish it twice.
- 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 Cursor 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 Cursor
With about 40 active tools allowed across every server, the schema tools may be among the ones you switched off to fit StoreSEO's 44. Before you start, open the StoreSEO entry in Cursor's MCP settings and confirm storeseo_list_schema_types, storeseo_get_schema_settings and storeseo_update_schema_settings are enabled, and keep the update on ask rather than in a run mode that lets it go through unprompted.
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 Cursor say it cannot find the StoreSEO schema update tool?
Cursor allows about 40 active tools across all servers and StoreSEO has 44, so you must switch some off. If storeseo_update_schema_settings was among them, turn it back on in the StoreSEO entry in MCP settings and switch off tools you use less.
Can Cursor change my theme and my StoreSEO schema in one go?
Yes, as two separate kinds of edit. The agent changes theme files through Cursor's editing tools, which you review as a diff, and changes StoreSEO schema settings through storeseo_update_schema_settings after you say yes.
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 Cursor guides