Gitscrum Core MCP server
io.github.gitscrum-core/mcp-server·v1.0.1·5 starsMCP server for GitScrum — manage tasks, sprints, time tracking, and client workflows via AI
5 stars115 downloads/wk
Reviews
Write oneNobody has reviewed Gitscrum Core yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Gitscrum Core tools (4)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
auth_completeComplete login after browser authorization.
auth_loginStart login. Returns URL and code for browser authorization.
auth_logoutLogout and clear token.
auth_statusCheck authentication status.
Public scan report
scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it
- Code scan59 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 228 days ago4/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
How Gitscrum Core compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 68/100
- higher than 30% of 48,255 servers
- Tools
- 4
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 5
- more than 83% of 28,688 servers
- Downloads a week
- 115
- more than 66% of 12,191 servers with a package
What its tools let an agent do: 4 read
Install Gitscrum Core in Claude Code, Cursor or VS Code
Runs npx -y @gitscrum-studio/mcp-server on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mcp-server -- npx -y @gitscrum-studio/mcp-server
What the publisher says
From the Gitscrum Core repository's README, as published. We do not edit it. Read it on GitHub
GitScrum MCP Server: Your AI Agent as a Project Manager 🚀
Turn your AI Agent into a full-scale Project Manager. The Official Model Context Protocol (MCP) server for GitScrum provides AI assistants (Claude, Cursor, Windsurf, Copilot) with deep context and operational access to your entire project stack.
⚡ Hosted (Recommended)
Zero install. Works everywhere.
https://mcp.gitscrum.com/sseSSE-based server hosted on AWS. Just add URL + token to your AI client.
Best for: Claude Desktop, Cursor, Windsurf, any SSE-compatible client.
→ Setup Guide
📦 Local (npm)
Self-hosted via npx.
npx -y @gitscrum-studio/mcp-serverRuns locally via stdio transport. Requires Node.js 18+.
Best for: VS Code, GitHub Copilot, offline environments.
→ Local Setup
Overview
GitScrum Studio MCP Server connects AI assistants to your GitScrum workspace via the Model Context Protocol. It gives Claude, GitHub Copilot, Cursor, and any MCP-compatible client full operational access to your project management stack — tasks, sprints, time tracking, user stories, epics, kanban workflows, team discussions, wiki, notes, client CRM, invoicing, proposals, budget tracking, analytics dashboards, standup reports, and activity feeds.
Everything your team does in the GitScrum web app, your AI assistant can now do through conversation.
You: "What's on my plate today?"
Assistant: Fetches your tasks due today across all projects.
You: "Create a sprint for next week with the top 5 backlog items"
Assistant: Creates the sprint, assigns tasks, and sets the timeline.
You: "Show me which projects are over budget"
Assistant: Returns burn-down data and flags at-risk projects.
You: "Send the Q1 proposal to Acme Corp"
Assistant: Creates the proposal, attaches the client, and sends it.
You: "What did the team ship this week?"
Assistant: Generates a standup digest with completed work and blockers.29 tools. 160+ operations. Zero context switching.
Quick start
Install
npx -y @gitscrum-studio/mcp-serverConfigure your client
Claude Desktop
Edit the configuration file:
- macOS: ~/Library/Application Support/Claude/claudedesktopconfig.json
- Windows: %APPDATA%\Claude\claudedesktopconfig.json
{
"mcpServers": {
"gitscrum": {
"command": "npx",
"args": ["-y", "@gitscrum-studio/mcp-server"]
}
}
}VS Code / Cursor
Add to .vscode/mcp.json or your MCP settings:
{
"servers": {
"gitscrum": {
"command": "npx",
"args": ["-y", "@gitscrum-studio/mcp-server"]
}
}
}Authenticate
Tell your AI assistant: "Login to GitScrum"
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Gitscrum Core: common questions
- Is Gitscrum Core MCP server safe?
- With care: it is graded C, so read the findings first (68/100). Read the Gitscrum Core safety report
- How do I install Gitscrum Core?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Gitscrum Core need an API key?
- Yes. The registry entry asks for
GITSCRUM_TOKEN. - Is Gitscrum Core maintained?
- The last commit was 264 days ago (2026-02-12). The latest release is v1.0.1.
- How does Gitscrum Core compare with other MCP servers?
- safety score 68/100 (higher than 30% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.