
Stride — AI software delivery platform
page.stridePublished by stride.pageOfficial publisherv1.0.0Updated Oct 25, 2026
Your team's stories, acceptance criteria, designs and docs, for coding agents. Sign in with OAuth.
Overview
Stride's remote MCP server lets a coding agent pull your team's stories, acceptance criteria, designs and docs, then check work and hand stories back for review
- What you can do
- Pick up a story with its acceptance criteria, linked designs, documents, relations and open defects, and move it to In Progress with a branch named after its key. Name a specific story key to pick up that one instead. Check a change against every acceptance criterion, run tests, and move the story to In Review with a comment on what changed, or report what remains unmet. Work within the project you choose and with your own permissions.
- When to use it
- Useful when your team tracks work in Stride and you want a coding agent to start from a full spec instead of a pasted ticket, and to close the loop by verifying acceptance criteria before review. Also suited to headless runs such as CI or scripted agent sessions.
- Requirements
- A remote endpoint at stride.page over streamable HTTP; no local package. OAuth sign-in through the browser is required, and you choose which project the agent works in. Headless runs need an agent key created in Stride, sent as an Authorization Bearer header.
Installation
In SourceWeft
- Open Stride — AI software delivery platform in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/page.stride%2Fstride/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"stride-ai-software-delivery-platform": {
"type": "http",
"url": "https://www.stride.page/api/mcp/stride"
}
}
}README
Stride plugins for Claude Code, Codex and Cursor
Work your Stride backlog from your coding agent. Two commands do the loop:
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
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?
Codex
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:
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: [email protected]. Licensed under the MIT License.
Source: README.md at commit fadb5c3
Tools
0Version history
1- v1.0.0LatestOct 25, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts