For Cursor users

Cursor with
persistent project memory.

Sprintra is the MCP server that gives Cursor persistent memory of your sprints, decisions, and knowledge base — readable from any chat through 20 MCP tools. No more pasting context into every prompt.

$npx create-sprintra
60-second install · MIT licensed · Free local mode
Featured on· Cursor Directory· MCP Registry· Glama· Smithery
What Cursor sees when you open a chat
# Sprintra Project Context (via MCP)

## Active Sprint
Sprint 28 · "Onboarding polish" · 5/8 stories done

## Recent Decisions
• Use shadcn/ui for the new dashboard (dec-3kF7Qn2)
• Drop Prisma, switch to Drizzle (dec-aBc91Yz)
• Move auth from NextAuth to Better Auth (dec-mN4xRp8)

## Open Stories
• VP-301 — Add billing portal (in_progress)
• VP-302 — Polish empty states
• VP-303 — Demo video freelancer brief

## Last Session Summary
Refactored auth to Better Auth. Pending: integration tests
for org-switching flow.

Cursor reads this through MCP every time you start a chat. No prompts to write, no docs to paste — Cursor just knows your project.

What Cursor can do once Sprintra is wired up.

Answer about old decisions

Architecture decision records with conflict detection. Ask Cursor what you decided about JWT 6 weeks ago — it pulls the actual ADR, not invented context.

Track sprint state

Active sprint, current stories, blockers — Cursor reads them and writes back. Say 'mark VP-301 done' and Cursor calls the MCP tool directly.

Cross-IDE memory

Same workspace readable from Claude Code, Codex, Antigravity, Gemini CLI. Pair-program in Claude, ship in Cursor — same project state in both.

How Cursor uses Sprintra.

  1. 1

    You open a Cursor chat.

    Cursor connects to the Sprintra MCP server (registered automatically by the installer). All 20 tools become available without any prompt engineering.

  2. 2

    Cursor pulls project context on demand.

    When you ask 'what's our auth approach?', Cursor calls Sprintra's decisions tool, gets the real ADR, and answers from project state — not invented from training data.

  3. 3

    You make a decision. Cursor writes it back.

    Say 'log this as a decision' and Cursor calls Sprintra's decisions.add tool. The decision is searchable from your next chat — and from Claude Code, Codex, anywhere.

  4. 4

    Switch to a different IDE. Same state.

    Open Claude Code on the same repo. Same Sprintra workspace, same memory, same decisions. The project context is the source of truth — not the IDE.

Install in 60 seconds.

One npx command. Auto-registers with Cursor's mcp.json. Local-first SQLite — your data stays on your machine.

$npx create-sprintra

Free Solo Pilot · MIT licensed · No credit card · No telemetry

FAQ

How does Sprintra give Cursor persistent memory?

Sprintra runs as an MCP (Model Context Protocol) server that Cursor connects to. It stores every decision, sprint, and project state — readable from any Cursor chat through 20 MCP tools (features, stories, sprints, decisions, knowledge base, dependencies, search, and more). Ask Cursor about any decision you've recorded, and it answers from real project state, not invented context.

How do I install Sprintra MCP in Cursor?

Run `npx create-sprintra` in your project directory. The installer auto-registers Sprintra MCP with Cursor's mcp.json config and seeds an initial project workspace. Total time: about 60 seconds. Local-first SQLite, no account required for the free Solo Pilot tier.

Is Sprintra free for Cursor users?

Solo Pilot tier is free forever — local SQLite, all 20 MCP tools, MIT licensed. No credit card. Hosted Team tier is $5 per seat per month for collaborative teams who want sync across machines plus dashboard access. The MCP server is open source on GitHub.

Does Sprintra work alongside Cursor's built-in memory?

Yes. Cursor's built-in memory is per-chat conversational context. Sprintra is a structured project workspace (sprints, decisions, knowledge base) that persists across all chats and even across IDEs. They complement each other — Cursor handles the conversation, Sprintra handles the project state.

Can I use the same Sprintra workspace across Cursor and Claude Code?

Yes — Sprintra MCP works with Cursor, Claude Code, Codex, Antigravity, and Gemini CLI. The same project workspace is readable and writable from any of these agents. Switch IDEs mid-feature without losing project context.

Will Sprintra capture sensitive code or credentials?

No. Sprintra captures structured project data (decisions, sprint state, project state) — not raw code or environment variables. In local mode (Solo Pilot), nothing leaves your machine. In hosted mode, per-user privacy is enforced by row-level security; cross-user reads require admin role. Three opt-out flags let you disable any capture layer.