Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for GitScrum — manage tasks, sprints, time tracking, and client workflows via AI
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
GITSCRUM_API_URL, GITSCRUM_TOKENValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"gitscrum-core": {
"command": "npx",
"args": [
"-y",
"@gitscrum-studio/mcp-server"
],
"env": {
"GITSCRUM_API_URL": "your-value",
"GITSCRUM_TOKEN": "your-value"
}
}
}
}Run this in your terminal
claude mcp add gitscrum-core --env GITSCRUM_API_URL=your-value --env GITSCRUM_TOKEN=your-value -- npx -y @gitscrum-studio/mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"gitscrum-core": {
"command": "npx",
"args": [
"-y",
"@gitscrum-studio/mcp-server"
],
"env": {
"GITSCRUM_API_URL": "your-value",
"GITSCRUM_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"gitscrum-core": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@gitscrum-studio/mcp-server"
],
"env": {
"GITSCRUM_API_URL": "your-value",
"GITSCRUM_TOKEN": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
GITSCRUM_API_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account gitscrum-core, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: GITSCRUM_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 9 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Signoff
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
Zero install. Works everywhere.
https://mcp.gitscrum.com/sse
SSE-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
Self-hosted via npx.
npx -y @gitscrum-studio/mcp-server
Runs locally via stdio transport. Requires Node.js 18+.
Best for: VS Code, GitHub Copilot, offline environments.
→ Local Setup
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.
npx -y @gitscrum-studio/mcp-server
Claude Desktop
Edit the configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": { "gitscrum": { "command": "npx", "args": ["-y", "@gitscrum-studio/mcp-server"] } } }
</details>
VS Code / Cursor
Add to .vscode/mcp.json or your MCP settings:
{
"servers": { "gitscrum": { "command": "npx", "args": ["-y", "@gitscrum-studio/mcp-server"] } } }
</details>
Tell your AI assistant: "Login to GitScrum"
The server initiates an OAuth 2.0 Device Authorization Grant flow. You authorize in the browser — credentials are never shared with the MCP server.
Each tool uses a consolidated action parameter, reducing LLM context tokens by ~80% compared to individual tool definitions.
| Tool | Actions | Docs |
|---|---|---|
task | my today get create update complete subtasks filter by_code duplicate move notifications | tasks |
sprint | list all get kpis create update stats reports progress metrics | sprints |
workspace | list get | projects |
project | list get stats tasks workflows types efforts labels members | projects |
time | active start stop logs analytics team reports productivity timeline | time-tracking |
| Tool | Actions | Docs |
|---|---|---|
user_story | list get create update all | user-stories |
epic | list create update | epics |
label | list create update attach detach toggle | labels |
task_type | list create update assign | task-types |
workflow | create update | workflows |
| Tool | Actions | Docs |
|---|---|---|
discussion | all channels channel messages send search unread mark_read create_channel update_channel | discussions |
comment | list add update | comments |
wiki | list get create update search | wiki |
note | list get create update share revisions | notevault |
note_folder | list create update move | notevault |
search | — | search |
| Tool | Actions | Docs |
|---|---|---|
client | list get create update contacts interactions add_interaction | clientflow |
invoice | list get stats create update issue send mark_paid | clientflow |
proposal | list get stats create update send approve reject convert | clientflow |
clientflow_dashboard | 8 reports | clientflow |
clientflow_cross_workspace | 4 reports | clientflow |
| Tool | Actions | Docs |
|---|---|---|
standup | summary completed blockers team stuck digest contributors | standup |
analytics | 10 reports | analytics |
activity | feed user_feed notifications activities task_workflow | activity |
budget | projects_at_risk overview consumption burn_down alerts events | budget |
| Tool | Description | Docs |
|---|---|---|
auth_login | Initiate device code flow | auth |
auth_complete | Complete authorization | auth |
auth_status | Check session status | auth |
auth_logout | Clear stored credentials | auth |
Full reference: docs/TOOLS.md
The server is designed around the principle of least privilege.
| Layer | Protection |
|---|---|
| Operations | Only CREATE, READ, UPDATE. DELETE is blocked at MCP and API layers. |
| Authentication | OAuth 2.0 Device Grant — credentials never touch the server. |
| Token storage | Local filesystem with restricted permissions. |
| Rate limiting | Automatic lockout after failed auth attempts. |
Destructive operations must be performed in the GitScrum Studio.
Full details: docs/SECURITY.md
Found a vulnerability? Report privately to security@gitscrum.com.
| [Hosted Server](docs/HOSTED.md) | SSE setup for Claude, Cursor, Windsurf, and more |
| [Usage Guide](docs/USAGE.md) | Practical examples and common workflows |
| [Tools Reference](docs/TOOLS.md) | All 29 tools with parameters and response shapes |
| [Per-Tool Guides](docs/tools/) | Deep-dive into each tool module |
| [Security](docs/SECURITY.md) | Security model, token handling, threat mitigations |
| [Development](docs/DEVELOPMENT.md) | Local setup, architecture, testing, contribution |
| [Changelog](CHANGELOG.md) | Version history and migration notes |
git clone https://github.com/gitscrum-core/mcp-server.git
cd mcp-server npm install npm run build npm test # 378 tests across 22 suites
Inspect locally with the MCP Inspector:
npx @modelcontextprotocol/inspector node dist/index.js
| Requirement | Version |
|---|---|
| Node.js | >= 18.0.0 |
| npm | >= 8.0.0 |
Full guide: docs/DEVELOPMENT.md
See CONTRIBUTING.md for guidelines.
git checkout -b feature/my-feature
npm test git commit -m "feat: describe your change"
MIT — see LICENSE.
Website · Docs · Issues · Changelog
Built by GitScrum