Mcp Server
Manage GitScrum tasks, sprints, time tracking, and client workflows from your AI agent instead of switching to a separate PM UI for every update.
Overview
GitScrum MCP Server is a MCP server for the Build phase that lets AI assistants manage GitScrum tasks, sprints, time tracking, and client workflows.
What is this MCP server?
- npm stdio package @gitscrum-studio/mcp-server version 1.0.1
- AI-facing access to GitScrum tasks, sprints, and time tracking
- Client workflow management through MCP tools
- Requires GITSCRUM_API_URL and GITSCRUM_TOKEN environment variables
- Targets agencies and studios on GitScrum, not generic GitHub issue sync
- Server schema version 1.0.1
- One npm stdio package: @gitscrum-studio/mcp-server at version 1.0.1
- Required env: GITSCRUM_API_URL (string), GITSCRUM_TOKEN (secret)
Community signal: 5 GitHub stars.
What problem does it solve?
You run delivery in GitScrum but your agent cannot see or update tasks and sprints, so every status change means leaving the coding session.
Who is it for?
Solo builders and small agencies on GitScrum who want conversational task, sprint, and time-tracking updates from their coding agent.
Skip if: Teams not using GitScrum, or builders who only need GitHub issues without sprint or client-workflow features.
What do I get? / Deliverables
After configuring API URL and token, your agent can query and mutate GitScrum work items and time data through MCP tools during build and client delivery.
- Agent-callable GitScrum tools for tasks, sprints, and time entries
- Authenticated stdio MCP connection using @gitscrum-studio/mcp-server 1.0.1
- In-chat client workflow updates without leaving the agent session
Recommended MCP Servers
Journey fit
Sprint and task orchestration while you are building maps to Build → pm because that is when solo builders plan and execute delivery work. GitScrum covers tasks, sprints, and client workflows—classic product management surfaces—not code integrations or deploy pipelines.
How it compares
GitScrum PM MCP over npm stdio, not GitHub repository automation or third-party PR risk screening.
Common Questions / FAQ
Who is GitScrum MCP Server for?
It is for developers and studios on GitScrum who want their MCP agent to handle tasks, sprints, time tracking, and client workflows without opening the GitScrum web app.
When should I use GitScrum MCP Server?
Use it during Build and client delivery when you are planning sprints, updating tasks, or logging time and want those actions driven from Claude Code, Cursor, or similar.
How do I add GitScrum MCP Server to my agent?
Install @gitscrum-studio/mcp-server via stdio in your MCP client and set GITSCRUM_API_URL to your GitScrum API base plus GITSCRUM_TOKEN as the secret API token.