An MCP server that shows coding agents the store behind a theme repository
Agents read a theme's outline, section schemas, the merchant content that names a setting, and metafield definitions, before they rename or remove anything. Read-only, and nothing is billed.
A coding agent sees the theme's code, but not what merchants did with it. The MCP server gives it the store: templates and section groups filled with content, theme settings, and files changed in the code editor.
Before an agent renames or removes a setting, block or section, it can check which of the store's content names it and would lose its values. It can read metafield and metaobject definitions before relying on them in Liquid, and read a pull request's preview theme instead of the published one.
Every tool is read-only and reads the store live. The server runs no model, so nothing is billed. It takes any team API key.
More in MCP server.