Integration

Connect Claude Code to your backlog

Stride exposes your backlog over the Model Context Protocol (MCP), so Claude Code, Codex and Cursor read and write real stories, sprints, tests, and architecture decisions, working from your connected delivery graph instead of code pasted into a chat window.

Why your AI agent needs your backlog

A coding agent is only as good as the context it can see. Point it at the repo alone and it writes plausible code for the wrong requirement. Stride gives the agent the structured context it’s missing (acceptance criteria, the linked test cases, the architecture decision that constrains the change, the sibling stories in the sprint) so it ships the feature you actually scoped, not just code that compiles.

How to connect it

  1. In Stride, open Settings → API keys and mint an AGENT key (scoped to the project you want the agent to work in).
  2. Add the Stride MCP server to your Claude Code config and set the key as a bearer token:
{
  "mcpServers": {
    "stride": {
      "type": "http",
      "url": "https://www.stride.page/api/mcp/stride",
      "headers": {
        "Authorization": "Bearer ${STRIDE_AGENT_KEY}"
      }
    }
  }
}

Claude Code discovers Stride’s tools automatically over MCP. There’s no plugin to install. Codex and Cursor work the same way — switch tabs above for the same endpoint in their own format.

What the agent can do

Stride exposes 120 RBAC-gated tools across all four modules. Every call is permission-checked by the dispatcher before it runs, and every write lands in the audit log as via: "mcp".

ModuleRepresentative tools
Planread a story’s full spec in one call (acceptance criteria, designs, docs, tests); create / update / search stories, epics, sprints, releases; bulk-update; open a GitHub draft PR from a story
Verifycreate test cases, fetch test runs, rerun failed tests, run quality-gate checks, get defects
Designread architecture diagrams (ERD, BPMN, C4 levels) and link them to stories; create / update / search documents and ADRs, append to a document
Optimizeget processes, list process insights, read delivery KPIs
Workspacelist members, manage labels, attachments, reactions, end session

Frequently asked questions

How do I connect Claude Code to Stride?

Create an AGENT API key in Settings → API keys, then add the Stride MCP server to your Claude Code config with the key as a bearer token. Claude Code discovers Stride’s tools automatically over MCP. No plugin to install.

Does Stride work with Codex and Cursor too?

Yes. All three use the same MCP backend; only the config format differs. Claude Code uses JSON, Codex uses TOML, and Cursor uses its own mcp.json, where the Authorization header must use Cursor’s ${env:NAME} interpolation rather than the bare ${NAME} form. All of them point at the same Stride MCP endpoint.

Is the MCP access permission-scoped?

Every MCP tool call is RBAC-gated by Stride’s dispatcher before the handler runs. AGENT keys carry an explicit project scope and an optional max-role cap, and every action is recorded in the audit log as via: "mcp".

What can the agent actually do?

Read and write stories, epics, sprints, releases, test cases, defects, documents, and ADRs, and query cross-module context like which open defects block a release. The agent works from your connected delivery graph instead of pasted snippets.

Which plan includes the MCP server?

Every paid plan includes MCP access, the public API, and webhooks. Starter includes one API or agent key and one webhook; Pro and Enterprise increase those limits. See the pricing page for the full breakdown.

Create a workspace, generate a scoped key, and connect Claude Code to the delivery record.

Get started
Defined in our glossary
Model Context Protocol (MCP)Acceptance criteria
Related reading