Building with a coding agent
The docs, the manifest schema, the API and your app, served to Claude Code, Codex or Cursor over MCP.
Early access
storeware mcp is an MCP server on stdio. Run in your app's folder, it gives a coding agent the Storeware docs and your app, so it looks a field up instead of guessing it.
Add it
Claude Code:
claude mcp add storeware -- npx @storeware/cli mcpCodex, in ~/.codex/config.toml:
[mcp_servers.storeware]
command = "npx"
args = ["@storeware/cli", "mcp"]Cursor, in .cursor/mcp.json:
{ "mcpServers": { "storeware": { "command": "npx", "args": ["@storeware/cli", "mcp"] } } }An app made by storeware init has the CLI as a development dependency, so in its folder npx @storeware/cli runs the version the app was made with rather than fetching one.
What it can do
| Tool | What it does |
|---|---|
search_docs | Finds docs pages by their words. |
read_docs_page | Reads one docs page as Markdown. |
manifest_schema | The JSON Schema of storeware.app.toml. |
api_operation | One call in the REST API, by its operation id or by words: method, path, parameters, body, answer and scopes. |
validate | Checks the manifest in the folder, and its scopes and events when you are signed in. |
preflight | Runs the checks a review runs, against your app on a development store. |
webhook_trigger | Sends your running app one signed event, and says how it answered. |
The last three act as you, with the sign-in storeware login saved, and reach only your development stores. The first four read public pages and need no sign-in.
The notes in every app
Every template storeware init writes has an AGENTS.md: how to install, check and run the app, where its files are, and the rules an agent would otherwise learn by breaking them, such as verifying the raw body before parsing it.