Sprrint MCP

Agents run Sprrint at https://mcp.sprrint.run/mcp. Same board as the website: tasks, sprints, releases, people. The agent acts with the permissions of the API key or OAuth grant you send.

It does not call other MCP servers. It is Sprrint, over MCP.

Start here

  1. Create a key in You → Keys (source: MCP)
  2. Connect your client — Cursor, Claude, or Slack OAuth
  3. Tool catalog
  4. Git-work skill — move the task, comment decisions, link the PR

The same JSON is on You → CLI & MCP in the app.

Slack as a channel bot (notifications, @Sprrint status) is a project integration, not MCP. See Slack.

How it works

Agent  --HTTPS-->  https://mcp.sprrint.run/mcp  -->  Sprrint

Every request sends Authorization: Bearer spr_live_…, or an OAuth access token from dynamic client registration (Slack). Optional headers: X-Workspace-Slug, X-Sprrint-Project.

A pinned X-Workspace-Slug does not hide other projects from sprrint_projects_list. That tool lists every project the token can see unless the call passes workspace. Other tools follow the header until the call passes workspace, or passes a project key that exists in only one workspace. See Tools.

No local install. Cursor, Claude, and any client that speaks remote MCP use that URL.

A sprrint mcp process in the CLI still exists for clients that only speak stdio. New setups use the hosted URL.

Safety