Gitscrum

com.gitscrumPublished by gitscrum.comv1.0.2Updated Oct 24, 2026

MCP server for GitScrum — manage tasks, sprints, time tracking, and client workflows via AI

VerifiedSTDIODesktop onlyProductivity & Workflow Communication & Collaboration Business & Commerce

Server details

Identifier: com.gitscrum/mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to gitscrum.com. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.gitscrum%2Fmcp.svg)](https://sourceweft.com/mcp/com.gitscrum%2Fmcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

GitScrum MCP server that lets an AI assistant manage projects, tasks, sprints, time tracking, wiki notes and client CRM inside a GitScrum workspace.

What you can do: Manage tasks, sprints, workspaces and projects, including subtasks, labels, task types and workflows, plus time tracking and reports. Plan work with user stories, epics and labels. Collaborate through discussions, channels, comments, wiki pages, notes and search. Handle client CRM records, invoices, proposals and dashboards. Read standup digests, analytics, activity feeds and budget risk reports. Sign in and out of GitScrum through device-flow authentication tools.
When to use it: Useful when a team already runs its projects, time tracking and client work in GitScrum and wants an assistant to query and update that data in conversation instead of switching to the web app.
Requirements: Runs locally as an npm package over stdio, requiring Node.js 18 or later and npm 8 or later. Needs a GitScrum API base URL in GITSCRUM_API_URL and an authentication token in GITSCRUM_TOKEN, or sign-in through the OAuth device flow. A hosted SSE endpoint is also described.

Before you install

The assistant can create and update records across projects, tasks, discussions, wiki, notes, clients, invoices and proposals, and can send invoices and proposals. Deletion is described as blocked, so destructive actions must be done in GitScrum itself. The token in GITSCRUM_TOKEN grants access to the workspace and is stored on the local filesystem.

Installation

In SourceWeft

Open Gitscrum in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[GitScrum]

GitScrum MCP Server: Your AI Agent as a Project Manager 🚀

[npm version] [MIT License] [Tests]

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.

[GitScrum MCP Server]

⚡ Hosted (Recommended)

Zero install. Works everywhere.

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

📦 Local (npm)

Self-hosted via npx.

Runs 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.

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

Configure your client

Claude Desktop

Edit the configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

json

{  "mcpServers": {    "gitscrum": {      "command": "npx",      "args": ["-y", "@gitscrum-studio/mcp-server"]    }  }}

{  "mcpServers": {    "gitscrum": {      "command": "npx",      "args": ["-y", "@gitscrum-studio/mcp-server"]    }  }}

VS Code / Cursor

Add to .vscode/mcp.json or your MCP settings:

json

{  "servers": {    "gitscrum": {      "command": "npx",      "args": ["-y", "@gitscrum-studio/mcp-server"]    }  }}

{  "servers": {    "gitscrum": {      "command": "npx",      "args": ["-y", "@gitscrum-studio/mcp-server"]    }  }}

Authenticate

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.

Tools

Each tool uses a consolidated action parameter, reducing LLM context tokens by ~80% compared to individual tool definitions.

Core

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

Planning

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

Collaboration

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

ClientFlow CRM

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

Insights ^PRO

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

Authentication

Full reference: docs/TOOLS.md

Security

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 [email protected].

Documentation


Hosted Server	SSE setup for Claude, Cursor, Windsurf, and more
Usage Guide	Practical examples and common workflows
Tools Reference	All 29 tools with parameters and response shapes
Per-Tool Guides	Deep-dive into each tool module
Security	Security model, token handling, threat mitigations
Development	Local setup, architecture, testing, contribution
Changelog	Version history and migration notes

Development

bash

git clone https://github.com/gitscrum-core/mcp-server.gitcd mcp-servernpm installnpm run buildnpm test          # 378 tests across 22 suites

git clone https://github.com/gitscrum-core/mcp-server.gitcd mcp-servernpm installnpm run buildnpm test          # 378 tests across 22 suites

Inspect locally with the MCP Inspector:

Full guide: docs/DEVELOPMENT.md

Contributing

See CONTRIBUTING.md for guidelines.

bash

git checkout -b feature/my-feature# make changes, add testsnpm testgit commit -m "feat: describe your change"

git checkout -b feature/my-feature# make changes, add testsnpm testgit commit -m "feat: describe your change"

License

MIT — see LICENSE.

Website · Docs · Issues · Changelog

Built by GitScrum

Source: README.md at commit 800279c

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

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

Requirement	Version
Node.js	>= 18.0.0
npm	>= 8.0.0

Gitscrum

Overview

Installation

In SourceWeft

Other MCP clients

README

GitScrum MCP Server: Your AI Agent as a Project Manager 🚀

⚡ Hosted (Recommended)

📦 Local (npm)

Overview

Quick start

Install

Configure your client

Authenticate

Tools

Core

Planning

Collaboration

ClientFlow CRM

Insights PRO

Authentication

Security

Documentation

Development

Contributing

License

Tools

Version history

Score

Insights ^PRO