← Documentation
Cursor IDE

Install Sprintra in Cursor

One command adds Sprintra to your Cursor workspace. Your agent gets project briefing, decision history, and SDLC traceability on every session.

One-command install
npx @sprintra/cli@latest plugin install \
  --ide=cursor \
  --project=<your-project-id>

Run from your project root. Writes the Sprintra MCP entry to .cursor/mcp.json and creates a .cursor/rules/sprintra-integration.mdc rule that tells Cursor to load context.

About Cursor's tool limit

Cursor caps total MCP tools at 40 across all servers combined. Sprintra ships 21 tools — leaving 19 for other servers. If you have other MCP servers installed (Linear, GitHub, etc.) and hit the limit, the agent silently loses access to some tools. A compact-mode build that exposes a smaller toolset is on the roadmap.

1. Set your API token

Cursor reads the token from the SPRINTRA_TOKEN environment variable via the ${env:SPRINTRA_TOKEN} reference in .cursor/mcp.json. Get yours from app.sprintra.io → account settings → API tokens.

export SPRINTRA_TOKEN="vp_your_token_here"

Add this to your ~/.zshrc / ~/.bashrc and restart Cursor so the new env var is picked up.

2. Verify the connection

Open Cursor Settings → MCP. You should see a sprintra entry with status enabled and 21 tools listed.

If the server doesn't appear, check your .cursor/mcp.json exists and Cursor was restarted after setting the token.

3. Test it in Cursor

Open Cursor Chat (⌘L / Ctrl+L) and ask:

"What's the latest on this project?"

The agent should call sprintra.ai(method: "generate_briefing") and return a rich briefing with active features, recent decisions, last session digest, top pending stories, and recent commits.

What you get

  • Project briefing on demand — recent decisions with rationale, where you left off, top pending stories, blocking questions
  • 21 MCP tools — stories, features, decisions, sprints, releases, notes, search, work_sessions, and more
  • Persistent memory across sessions — every Cursor chat starts with full context, no manual summarizing
  • Decision tracking — agents can record architectural decisions with the rationale, surfaced in future sessions
  • Cross-IDE continuity — switch between Cursor, Claude Code, and Codex on the same project; the briefing follows you

Common issues

Sprintra doesn't appear in MCP settings

Make sure .cursor/mcp.json exists in your project root and contains the sprintra entry. After adding the file, fully restart Cursor (not just reload the window).

"project_id is required"

The agent didn't pass project_id on its MCP call. Check .cursor/rules/sprintra-integration.mdc — it should have a 🔑 Project ID (REQUIRED) block. If missing, re-run npx @sprintra/cli plugin install --ide=cursor --project=<id>.

Some Sprintra tools are missing from the agent

You've probably hit Cursor's 40-tool ceiling across all MCP servers. Disable other MCP servers you aren't using, or wait for our compact-mode build.

Authentication errors / 401 from sprintra.io

Token isn't being passed. In a terminal where you started Cursor, verify echo $SPRINTRA_TOKEN returns your token. Cursor inherits env vars from the shell that launched it — if you started Cursor from the dock, set the env var via launchctl setenv (macOS) and re-launch.

Need an account?

Sprintra Cloud is free to start. Sign up, create a project, and copy your project ID into the install command above.

Sign up free

Using a different AI tool?

Claude CodeCodex CLIAntigravityGemini CLI