Integration
Connect Claude Code to your backlog
Stride exposes your backlog over the Model Context Protocol (MCP), so Claude Code and Codex 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
- In Stride, open Settings → API keys and mint an AGENT key (scoped to the project you want the agent to work in).
- Add the Stride MCP server to your Claude Code config and set the key as a bearer token:
{
"mcpServers": {
"stride": {
"url": "https://www.stride.page/api/mcp",
"headers": { "Authorization": "Bearer ${STRIDE_AGENT_KEY}" }
}
}
}Claude Code discovers Stride’s tools automatically over MCP — there’s no plugin to install. Codex works the same way; it just uses TOML instead of JSON for the same endpoint.
What the agent can do
Stride exposes 70+ 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".
| Module | Representative tools |
|---|---|
| Plan | create / update / search stories, epics, sprints, releases; bulk-update; sprint metrics |
| Verify | create test cases, fetch test runs, rerun failed tests, run quality-gate checks, get defects |
| Design | create / update / search documents and ADRs, append to a document |
| Optimize | get processes, list process insights, read delivery KPIs |
| Workspace | list 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 too?
Yes. Codex uses the same MCP backend; the only difference is config format — Codex uses TOML, Claude Code uses JSON. Both 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?
The MCP server, public API, and webhooks are included on the Pro plan ($29/seat/mo) and Enterprise. See the pricing page for the full breakdown.
Plug Claude Code into a real backlog in under two minutes.
Start free- How AI writes acceptance criteria (and where it fails)The honest map of where AI is dramatically better than humans at writing acceptance criteria — and the five places it confidently writes garbage. Plus the prompts that work.10 min read
- The connected delivery graph: one source of truth from PRD to prodMost teams ship software with five tools that don't talk to each other. The friction isn't any individual tool — it's the missing graph between them. This is the case for one connected graph.9 min read