Koskamo

Stride MCP

An official MCP server that connects AI coding agents to the Stride software delivery platform. It allows agents to read and write backlog items, manage sprints, verify test cases, access architecture diagrams, and track delivery KPIs using 131 RBAC-gated tools.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Stride MCP logo, by StrideVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by Stride
You need:Sign in with your Stride accountuse an agent key insteadGenerate Agent KeyPut the key in an environment variable
MCP endpoint (Streamable HTTP)
https://www.stride.page/api/mcp/stride
Vendor documentation

What you can do with it

  • Read story specs including acceptance criteria and linked tests
  • Create, update, and search stories, epics, and sprints
  • Verify test cases and fetch test runs
  • Read architecture diagrams and link them to stories

Source and maintenance

Vendor evidenceRegistry 1.0.0
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
281 ms
95th percentile latency
281 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 281 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http stride-mcp https://www.stride.page/api/mcp/stride

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add stride-mcp --url https://www.stride.page/api/mcp/stride

Cursor

Merge this server into .cursor/mcp.json in your project, then enable stride-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "stride-mcp": {
      "url": "https://www.stride.page/api/mcp/stride"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "stride-mcp": {
      "type": "streamableHttp",
      "url": "https://www.stride.page/api/mcp/stride",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start stride-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "stride-mcp": {
      "type": "http",
      "url": "https://www.stride.page/api/mcp/stride"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http stride-mcp https://www.stride.page/api/mcp/stride

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "stride-mcp": {
      "url": "https://www.stride.page/api/mcp/stride"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "stride-mcp": {
      "serverUrl": "https://www.stride.page/api/mcp/stride"
    }
  }
}

Let your agent find its tools

Find servers like Stride MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Stride MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing