Sprintra
Give Claude Code or Cursor a persistent project brain—sprints, decisions, memory, and a knowledge base—without re-explaining context every session.
Overview
Sprintra is a MCP server for the Build phase that exposes memory, decisions, sprints, and a knowledge base as tools for AI coding agents.
What is this MCP server?
- MCP tools for memory, decisions, sprints, and a project knowledge base aimed at AI coding agents
- Remote streamable-http endpoint (api.sprintra.io) plus stdio via npx @sprintra/mcp
- VIBEPILOT_MODE local (SQLite) or saas (PostgreSQL + SUPABASE_DATABASE_URL)
- Optional GEMINI_API_KEY for embedding-based decision conflict detection
- Catalog version 1.0.4 with npm package 1.0.3 and GitHub source sprintra-mcp
- Server catalog version 1.0.4; npm @sprintra/mcp package version 1.0.3
- Two connection paths: streamable-http remote URL and stdio transport
- Three documented environment variables (VIBEPILOT_MODE, SUPABASE_DATABASE_URL, GEMINI_API_KEY)
Community signal: 2 GitHub stars.
What problem does it solve?
Agents lose project context between sessions, so you repeat decisions, miss sprint intent, and ship inconsistent implementations.
Who is it for?
Solo builders running multi-week agent-assisted products who want SQLite locally or PostgreSQL in saas mode with optional Gemini conflict checks on decisions.
Skip if: Teams that only need ephemeral chat, already standardize on a single PM suite with no MCP bridge, or cannot host secrets for database URLs.
What do I get? / Deliverables
After you register Sprintra, your agent can read and update structured project memory, decisions, and sprint state through MCP instead of guessing from chat alone.
- MCP-connected project memory, decisions, sprint, and knowledge-base tools for your coding agent
- Repeatable agent sessions that reference stored decisions instead of re-deriving them
Recommended MCP Servers
Journey fit
Sprintra is canonical on Build because it is where solo builders wire agent tooling and run day-to-day execution (sprints, decisions, KB) while shipping. PM is the best shelf: the server centers sprints, recorded decisions, and structured project memory rather than a single API or UI task.
How it compares
MCP project-memory integration, not a standalone brainstorming or planning skill inside the repo.
Common Questions / FAQ
Who is Sprintra for?
Sprintra is for indie and solo developers using Claude Code, Cursor, or Codex who want a durable project brain—memory, decisions, sprints, and KB—wired through MCP.
When should I use Sprintra?
Use Sprintra when a product outgrows one-shot prompts and you need agents to honor recorded decisions and sprint work across sessions, especially during Build and ongoing iteration.
How do I add Sprintra to my agent?
Add the remote MCP URL https://api.sprintra.io/api/mcp for streamable-http, or run npx @sprintra/mcp with VIBEPILOT_MODE and database env vars; set GEMINI_API_KEY only if you want embedding-based decision conflict detection.