Connect Sprrint MCP

URL: https://mcp.sprrint.run/mcp

1. Create a key

Open Sprrint → You → Keys. Name the key, set use to MCP, create it, copy it once.

You → CLI & MCP already has the JSON below.

2. Cursor

~/.cursor/mcp.json or project .cursor/mcp.json:

{
  "mcpServers": {
    "sprrint": {
      "url": "https://mcp.sprrint.run/mcp",
      "headers": {
        "Authorization": "Bearer spr_live_your_key",
        "X-Workspace-Slug": "acme",
        "X-Sprrint-Project": "BR"
      }
    }
  }
}

X-Workspace-Slug and X-Sprrint-Project are optional. Without a project header, pass project on each tool, or the server uses your last opened project when you only have one.

A header pins the active workspace. It does not limit sprrint_projects_list: that call returns every project you can see, with each project's workspace slug, until you pass workspace. Pass workspace on any other tool to use that workspace for that call. A project key that exists in only one workspace resolves on its own. The same key in two workspaces returns ambiguous_project until you pass workspace.

Replace spr_live_your_key with the key from step 1. Restart Cursor (or reload MCP) and ask: “What is on Now in Sprrint?”

3. Claude Desktop

claude_desktop_config.json uses the same block:

{
  "mcpServers": {
    "sprrint": {
      "url": "https://mcp.sprrint.run/mcp",
      "headers": {
        "Authorization": "Bearer spr_live_your_key"
      }
    }
  }
}

4. Check it

GET https://mcp.sprrint.run/health returns {"ok": true} with no key.

A tool call without Authorization: Bearer spr_live_… returns 401. With a real key, ask the client to run sprrint_whoami.

5. Local stdio

Clients that cannot open a URL can still run the CLI process:

pipx install sprrint
{
  "mcpServers": {
    "sprrint": {
      "command": "sprrint",
      "args": ["mcp"],
      "env": {
        "SPRRINT_API_KEY": "spr_live_your_key",
        "SPRRINT_PROJECT": "BR"
      }
    }
  }
}

That process reads ~/.config/sprrint/config.toml when env is omitted, and it calls https://sprrint.run. Hosted clients send X-Sprrint-Project instead of SPRRINT_PROJECT.

6. Slack MCP (agent in Slack)

This is not the project Slack bot. The bot posts to a channel and answers @Sprrint status — that setup is Slack.

This section is a Slack agent that runs Sprrint tools as you (create tasks, move work, comment). Slack’s custom MCP form has no API-key field. Use Dynamic client registration. The hosted server registers Slack, then sends the person who connects to Sprrint to sign in and allow access.

  1. Server URL: https://mcp.sprrint.run/mcp
  2. Authentication: Dynamic client registration
  3. Identity URL (optional): https://mcp.sprrint.run/oauth/userinfo
  4. Account identifier (optional): $.id

Leave the identity fields empty if you only need the connection. Fill them when each Slack user should map to their own Sprrint account.

Continue. Slack opens Sprrint. Sign in, choose Allow. The agent then acts as that Sprrint user. API keys from You → Keys keep working for Cursor and Claude.

After it connects, the same tools as Cursor apply, including git links. Point the Slack agent at the git-work skill if it should move tasks and comment while coding.