Integration
Connect Codex to your delivery record
Model Context Protocol (MCP) is an open standard that lets Codex use approved tools and context from Stride. Codex can work from linked stories, decisions, diagrams, processes, and tests instead of reconstructing intent from a repository alone.
How to connect Codex
- In Stride, open Settings → Integrations → Codex and generate a project-scoped agent key.
- Export it as
STRIDE_AGENT_KEYin the environment that launches Codex. - Add the TOML configuration below to
~/.codex/config.toml, or to.codex/config.tomlin a trusted project.
[mcp_servers.stride]
url = "https://www.stride.page/api/mcp/stride"
bearer_token_env_var = "STRIDE_AGENT_KEY"What Codex can do
Stride exposes 119 unique, externally callable tools. Access is constrained by the member, workspace, project scope, and role associated with the agent key.
| Module | Representative work |
|---|---|
| Plan | Read connected story context; create and update stories, epics, sprints, and releases. |
| Design | Read diagrams and architecture decisions; create, update, and link documents and ADRs. |
| Optimize | Read processes, process insights, delivery KPIs, and linked modernization context. |
| Verify | Create test cases, inspect test runs and defects, and run release quality-gate checks. |
Frequently asked questions
How do I connect Codex to Stride?
In Stride, open Settings → Integrations → Codex and generate an agent key scoped to the projects Codex should reach. Export that key as STRIDE_AGENT_KEY, then add the supplied TOML block to ~/.codex/config.toml or a trusted project’s .codex/config.toml.
What does the Codex configuration contain?
The configuration names the Stride MCP endpoint and tells Codex to read its bearer token from STRIDE_AGENT_KEY. The secret stays in your environment instead of being written into config.toml.
Can Codex change project data?
Yes, when the member and project-scoped key permits it. Every tool call is checked by Stride before its handler runs, and writes are recorded as MCP activity for the identity that created the integration.
Does the same connection work with Claude Code and Cursor?
All three clients use the same Stride MCP endpoint and tool registry. Their configuration formats differ, so use the matching setup guide and give each client its own scoped key.
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. The pricing page contains the current plan details.
- 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