Stride MCP server
Commit Oct 24, 2026Connects coding agents to your software delivery backlog to manage stories, acceptance criteria, and designs.
Also known as Newlight-Solutions/stride-plugins, stride-plugins
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.0
- Last commit
- Oct 24, 2026
- License
- MIT
What is Stride MCP?
Stride connects coding agents to your software delivery backlog to manage stories, acceptance criteria, and designs.
Summary generated from the project's README
About Stride MCP server
Stride connects coding agents like Claude Code, Codex, and Cursor to your software delivery backlog. It allows developers to manage stories, acceptance criteria, and designs directly from their coding environment. The server functions by pulling staged stories or assigned tasks from an active sprint, providing full specifications, linked documents, and open defects in a single call. It also handles the transition of stories from In Progress to In Review by verifying changes against requirements.
Users set up the connection via a browser-based sign-in process rather than copying API keys, though headless environments like CI can use an agent key. The integration respects existing project permissions and labels all agent-generated work accordingly. Developers can use specific commands like /stride:next to pick up a task and create a new branch, or /stride:done to run tests and check acceptance criteria before pushing code.
What you can do with it
- 1Automate story pickupAsk your agent to retrieve the next assigned story along with its full specification and design documents.
- 2Verify acceptance criteriaHave the agent check the implemented changes against the defined requirements before moving the task to review.
- 3Manage task statusInstruct the agent to move a story to the In Progress state and create a corresponding branch.
- 4Run headless automationUse an agent key to allow CI or command-line tools to interact with the Stride backlog without a browser.
Written from the project's README. Every use case is checked against a quote from it.
How to install Stride MCP
Formats verified 10 Nov 2026Install Stride MCP in Claude Code
$ claude mcp add --transport http stride-plugins https://www.stride.page/api/mcp/strideInstall Stride MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"stride-plugins": {
"url": "https://www.stride.page/api/mcp/stride"
}
}
}Install Stride MCP in VS Code
.vscode/mcp.json
{
"servers": {
"stride-plugins": {
"type": "http",
"url": "https://www.stride.page/api/mcp/stride"
}
}
}Install Stride MCP in Codex
~/.codex/config.toml
[mcp_servers.stride-plugins] url = "https://www.stride.page/api/mcp/stride"
Install Stride MCP in Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"stride-plugins": {
"httpUrl": "https://www.stride.page/api/mcp/stride"
}
}
}README
View on GitHubStride plugins for Claude Code, Codex and Cursor
Work your Stride backlog from your coding agent. Two commands do the loop:
| Claude Code | Codex | Cursor | |
|---|---|---|---|
| Pick up your next story, with its full spec, and start it | /stride:next |
$stride:next |
/stride-next |
| Check it against its acceptance criteria and hand it back for review | /stride:done |
$stride:done |
/stride-done |
Next pulls the story a teammate staged for you with "Hand to your agent"
or, when nothing is staged, the top story assigned to you that is still to do
(the active sprint first, then by priority). You get its acceptance criteria,
linked designs and documents, relations and open defects in one call. It moves
the story to In Progress and sets up a branch named after its key. Name a key
(/stride:next ORB-526) to pick up a particular story.
Done runs your tests, checks every acceptance criterion against the change, and moves the story to In Review with a comment saying what changed. If a criterion is not met, it says what remains and leaves the status alone. It asks before committing, and pushes only when you ask.
Every plugin connects your agent to Stride's MCP server,
https://www.stride.page/api/mcp/stride. You sign in to Stride in your
browser; there is no key to copy. You choose the project the
agent works in and the projects it can reach, and you can disconnect it at any
time in Stride under Settings → Integrations → Connected apps. The agent
works with your own permissions in each project, and everything it writes is
labeled as your agent's.
Claude Code
claude plugin marketplace add Newlight-Solutions/stride-plugins
claude plugin install stride@stride
Or, inside a session: /plugin marketplace add Newlight-Solutions/stride-plugins,
then /plugin install stride@stride.
Then run /mcp, select plugin:stride:stride, and choose Authenticate.
Your browser opens to sign in to Stride. After that, run /stride:next.
Prefer the server without the commands?
claude mcp add --transport http stride https://www.stride.page/api/mcp/stride
Codex
codex plugin marketplace add Newlight-Solutions/stride-plugins
Then start codex, run /plugins, open Stride AI and install it. Codex
asks you to sign in to Stride when you install. Start a new session, then run
$stride:next.
Cursor
Copy the cursor folder to ~/.cursor/plugins/local/stride and
run Developer: Reload Window. Then open Customize → MCPs, where Stride
shows that it needs to sign in, and follow its prompt; your browser opens to
sign in to Stride. After that, run /stride-next in chat. (On Enterprise,
Cursor loads local plugins only when an admin allows local plugin imports.)
On a Teams or Enterprise plan, an admin can instead import this repository as a team marketplace (Dashboard → Plugins & MCPs → Add Marketplace → Import from Repo), and everyone installs Stride from Customize. Once Stride is listed in the Cursor Marketplace, anyone can install it from Customize: find Stride and select Install.
Prefer the server without the commands? Add it to ~/.cursor/mcp.json:
{
"mcpServers": {
"stride": { "url": "https://www.stride.page/api/mcp/stride" }
}
}
Using an agent key instead
Headless runs (CI, claude -p, codex exec) cannot open a browser to sign in.
For those, create an agent key in Stride under Settings → Integrations and send
it as Authorization: Bearer <key>. Setup for each agent:
Claude Code,
Codex,
Cursor.
This repository
claude-code/,codex/andcursor/are the three packages, each in its agent's own format. They are generated: editsource/and runnpm run build.codex/is also the package submitted to OpenAI's plugin directory (ChatGPT and Codex), as Stride AI, with its review material. It carries its own version, so a directory release leaves the other two packages alone..claude-plugin/marketplace.json,.agents/plugins/marketplace.jsonand.cursor-plugin/marketplace.jsonare the marketplaces the install commands above read.server.jsonis Stride's entry in the MCP Registry.npm run checkrebuilds nothing; it fails if a package has drifted fromsource/or breaks a rule its agent documents. CI runs it on every push.
Questions or problems: info@newlightai.com. Licensed under the MIT License.
Stride MCP questions
How do I add Stride MCP to Claude Code?
Run claude mcp add --transport http stride-plugins https://www.stride.page/api/mcp/stride in your terminal. Add --scope user to make it available in every project.
How do I add Stride MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Can the agent verify if my work meets the requirements?
Yes, the 'Done' command runs tests and checks every acceptance criterion against the changes to ensure requirements are met.