MCP tools reference.
Stori hosts an MCP server at https://stori.zone/api/mcp exposing the full API as MCP tools. Connect over HTTP, authorize in the browser, no install. The sections below cover the most common reads and writes. Your agent sees every tool the server exposes via the MCP `tools/list` capability — use search_documentation to find ones not listed here (canvas areas, releases, billing, ops log, &c.).
One-line install (recommended)
Auto-detects your MCP client (Claude Code, Cursor, Codex, Cline, Continue, Windsurf, Claude Desktop), emails you a verification link, then writes the right config block:
curl https://stori.zone/install | sh
Enter your email when prompted. Click the verification link in your inbox. The script writes an API key into your client's config and prints "Done. Restart <client> to load the MCP server."
If multiple MCP clients are detected, the script asks which one to install for. For CI / agent-driven installs, pass --non-interactive --email=<addr> --client=<name> — valid client names: claude-code, codex, cursor, cline, continue, windsurf, claude-desktop.
Pass --scope=project to write a project-level config in the current directory instead of the user-global one — supported for claude-code (writes .mcp.json) and cursor (writes .cursor/mcp.json). Interactive installs ask which scope when both apply.
Other clients (manual install)
If the one-line installer doesn't fit your setup (different MCP client, locked-down machine, syncing config across hosts), generate an API key at /account → API keys, then paste the block for your client below — replace <API_KEY> with the key you generated.
If the Claude Code CLI is on your PATH, the easiest path is OAuth — no API key needed:
claude mcp add --transport http stori https://stori.zone/api/mcp
Then run /mcp inside Claude Code to authorize in the browser. Otherwise add this to ~/.claude.json:
{
"mcpServers": {
"stori": {
"type": "http",
"url": "https://stori.zone/api/mcp",
"headers": { "Authorization": "Bearer <API_KEY>" }
}
}
}