Docs · Getting started

Stori, end to end.

One morphing canvas, configurable workflows, TraQL, an MCP server baked in. This is the developer reference.

REST API Reference

Full endpoint documentation with examples

TraQL Reference

Query language syntax and examples

MCP Tools

Model Context Protocol integration

Workflows

Configurable workflow states

GitHub

Connect a repo, link activity, automate states

Roles & Permissions

Role hierarchy and capability matrix

Key concepts

Projects

Projects are the top-level container. Each project has a unique 2–5 character key (e.g. PIC, TRK), its own workflow configuration, buckets, and work items. Projects can be public or private.

Work Items

Work items come in three types: task, bug, idea. Each has a state, optional assignee, and tags. Items link to each other via explicit relationships (blocks, relates_to, duplicates). All work items live on the canvas — drag, lasso-select, drop into magnetic areas that pull cards in by attribute.

Buckets & canvas axis

Work items triage into three planning buckets — Now / Next / Later. Magnetic areas partition the canvas by one attribute at a time: the canvas axis is bucket (Now / Next / Later), status (your workflow states), or release. Switch the axis in any view and cards animate into their new areas. There are no dated sprints — buckets are the planning surface.

Workflow States

Each project has a configurable set of workflow states. Every state belongs to one of three categories: todo, in_progress, or done. States have a display name, slug, color, and position. You can use presets (simple, standard, delivery_pipeline) or build your own.

TraQL

Stori Query Language — a structured query language for searching and aggregating work items. Supports field filters, hierarchy traversal, date arithmetic, cross-project queries, sorting, and aggregations. See the TraQL Reference for full syntax.

Getting started with the API

Base URL

https://app.stori.zone/api

Authentication

Include a Bearer token in the Authorization header. Public endpoints (listing projects) may work without auth.

Authorization: Bearer <your-token>

Quick example

1. Create a project

curl -X POST https://app.stori.zone/api/projects \
  -H "Content-Type: application/json" \
  -d '{"name": "My Project", "key": "MYP"}'

2. Create a work item

curl -X POST https://app.stori.zone/api/projects/STRI/work-items \
  -H "Content-Type: application/json" \
  -d '{"title": "Build login page", "type": "task"}'

3. List work items

curl -X POST https://app.stori.zone/api/traql \
  -H "Content-Type: application/json" \
  -d '{"query": "project:STRI is:open"}'

See the REST API Reference for full endpoint documentation.

Getting started with MCP

The Stori MCP server lets AI assistants like Claude interact with Stori directly — creating projects, managing work items, running TraQL queries, and more.

1. Install with one command

curl https://app.stori.zone/install | sh

Detects your MCP client (Claude Code, Cursor, Codex, Cline, Continue, Windsurf, Claude Desktop), asks for an email, sends a verification link, then writes the right config block. Pass --non-interactive --email=<addr> --client=<name> for CI / agent-driven installs.

2. Or wire it up by hand

Use claude mcp add or paste this block into your client's MCP config. Then run /mcp in Claude Code (or the equivalent in your client) — your browser opens Stori’s consent screen; approve once and the token is stored.

claude mcp add --transport http stori https://app.stori.zone/api/mcp

{
  "mcpServers": {
    "stori": {
      "type": "http",
      "url": "https://app.stori.zone/api/mcp"
    }
  }
}

3. Use in your client

Once configured, Claude can call tools like save_work_item, get_work_item, and query_work_items directly.

See the MCP Tools page for the full list of available tools.