Sprrint MCP

The Sprrint MCP server is the same product as the website and the CLI. An agent that only speaks MCP can run the board, write tasks, move cards, manage sprints, and invite people — with the same permissions as the person who owns the API key.

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

Start here

1. Install the sprrint CLI
2. Create a key in You → Keys (source: MCP) or run sprrint login
3. Connect your client
4. Tool catalog

How it works

Agent  --stdio-->  sprrint mcp  --HTTPS Bearer-->  /api/v1  -->  Sprrint

The server is stateless besides the key. It always calls https://sprrint.run and reads SPRRINT_API_KEY or ~/.config/sprrint/config.toml.

Why a separate package

The MCP server is open source (sprrint-cli) so editors can pin a version without pulling the Django app. The Django app only exposes /api/v1 and the Keys / CLI & MCP profile tabs.

Safety

• Keys are hashed at rest. The full token is shown once.
• Revoke a key from You → Keys and every MCP client using it stops.
• Destructive tools (projects_delete, workspace role changes) require the same confirmations as the website.
• The agent acts as you. It can only see and change what you can.