Gitscrum Core

io.github.gitscrum-corePublished by GitHub account gitscrum-corev1.0.1Updated Oct 24, 2026

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

The publisher's own server: core.blue

VerifiedSTDIODesktop onlyProductivity & Workflow Communication & Collaboration Business & Commerce

Server details

Identifier: io.github.gitscrum-core/mcp-server
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 the GitHub account gitscrum-core for this listing. That does not show the account is the product's maker.

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/io.github.gitscrum-core%2Fmcp-server.svg)](https://sourceweft.com/mcp/io.github.gitscrum-core%2Fmcp-server?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

GitScrum project-management MCP server that lets an AI assistant read and manage tasks, sprints, time tracking, wiki notes, CRM clients, invoices and proposals.

What you can do: Manage tasks and sprints: list, create, update, complete, move and filter tasks, and create or report on sprints and KPIs. Browse workspaces and projects with their stats, workflows, labels and members. Track time: start and stop timers, view logs, team reports and productivity analytics. Plan work with user stories, epics, labels, task types and workflows. Collaborate through discussions, comments, wiki pages, notes and search. Handle ClientFlow CRM clients, invoices and proposals, plus standup digests, activity feeds and budget reports.
When to use it: Useful when a team already runs its projects, time tracking and client work in GitScrum and wants an assistant to answer questions or make routine updates without switching apps. Suited to conversational task and sprint management, standup and budget reporting, and drafting or sending client invoices and proposals.
Requirements: Runs locally as an npm package over stdio and needs Node.js 18 or later. Requires a GitScrum account and API access: the GITSCRUM_API_URL base URL and the GITSCRUM_TOKEN secret. The README also describes a hosted SSE endpoint and an OAuth device login flow.

Before you install

The token grants access to the whole GitScrum workspace, so treat it as a secret. The assistant can create and update records, including sending invoices and proposals and posting discussion messages, which may reach clients or teammates. Deletion is blocked by design, but destructive changes must be made in the GitScrum web app.

Installation

In SourceWeft

Open Gitscrum Core 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.1LatestSep 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

Other Core integrations

core.blue

blue.coreOfficial publisher

Remote MCP endpoint for core.blue's private per-customer agent memory "houses": read its manual, try a sandbox, get pricing and recommendations, and request a…

Streamable HTTPWeb executable

Business & Commerce10 toolsNov 4, 2026

Brevio Core

Published by GitHub account Brevio-Ventures

Local MCP server that lets a coding agent scan code for recurring agent-written mistakes, explain rules, list rules and turn a fix into a guard.

STDIODesktop only

Developer ToolsNot validated yetNov 7, 2026

brain-core

Published by GitHub account xy-claude

Local MCP server that gives a Claude Code agent persistent memory across sessions, stored as markdown files plus a SQLite and vector index on your disk.

STDIODesktop only

Developer ToolsNot validated yetNov 7, 2026

Scovant Core

Published by GitHub account Scovant

Passive AI-agent readiness scan of a website: robots, llms.txt, JSON-LD, MCP discovery, security.

STDIODesktop only

AI & MLNot validated yetNov 3, 2026

ProofCore

Published by GitHub account ProofCore-Protocol

Zero-Auth Cryptographic Notarization & Evidence Layer on TON Blockchain for AI Agents.

Streamable HTTPWeb executable

AI & ML4 toolsNov 3, 2026

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 Core

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

Other Core integrations

core.blue

Brevio Core

brain-core

Scovant Core

ProofCore

Insights ^PRO