io.github.gitscrum-core/mcp-server

Official registry AI and agents

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

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @gitscrum-studio/mcp-server
Claude Code
claude mcp add io-github-gitscrum-core-mcp-server -e 'GITSCRUM_API_URL=<GITSCRUM_API_URL>' -e 'GITSCRUM_TOKEN=<your gitscrum_token>' -- npx -y @gitscrum-studio/mcp-server@1.0.1
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "io-github-gitscrum-core-mcp-server": {
            "command": "npx",
            "args": [
                "-y",
                "@gitscrum-studio/mcp-server@1.0.1"
            ],
            "env": {
                "GITSCRUM_API_URL": "<GITSCRUM_API_URL>",
                "GITSCRUM_TOKEN": "<your gitscrum_token>"
            }
        }
    }
}

Environment variables

  • GITSCRUM_API_URL GitScrum API base URL
  • GITSCRUM_TOKEN secret GitScrum API authentication token

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. GitScrum MCP Server: Your AI Agent as a Project Manager 🚀
  2. Overview
  3. Quick start
  4. Tools
  5. Security
  6. Documentation
  7. Development
  8. Contributing
  9. License

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

📦 Local (npm)

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


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-server
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
{
  "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"

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
ToolActionsDocs
taskmy today get create update complete subtasks filter by_code duplicate move notificationstasks
sprintlist all get kpis create update stats reports progress metricssprints
workspacelist getprojects
projectlist get stats tasks workflows types efforts labels membersprojects
timeactive start stop logs analytics team reports productivity timelinetime-tracking
Planning
ToolActionsDocs
user_storylist get create update alluser-stories
epiclist create updateepics
labellist create update attach detach togglelabels
task_typelist create update assigntask-types
workflowcreate updateworkflows
Collaboration
ToolActionsDocs
discussionall channels channel messages send search unread mark_read create_channel update_channeldiscussions
commentlist add updatecomments
wikilist get create update searchwiki
notelist get create update share revisionsnotevault
note_folderlist create update movenotevault
search—search
ClientFlow CRM
ToolActionsDocs
clientlist get create update contacts interactions add_interactionclientflow
invoicelist get stats create update issue send mark_paidclientflow
proposallist get stats create update send approve reject convertclientflow
clientflow_dashboard8 reportsclientflow
clientflow_cross_workspace4 reportsclientflow
Insights PRO
ToolActionsDocs
standupsummary completed blockers team stuck digest contributorsstandup
analytics10 reportsanalytics
activityfeed user_feed notifications activities task_workflowactivity
budgetprojects_at_risk overview consumption burn_down alerts eventsbudget
Authentication
ToolDescriptionDocs
auth_loginInitiate device code flowauth
auth_completeComplete authorizationauth
auth_statusCheck session statusauth
auth_logoutClear stored credentialsauth

Full reference: docs/TOOLS.md


Security

The server is designed around the principle of least privilege.

LayerProtection
OperationsOnly CREATE, READ, UPDATE. DELETE is blocked at MCP and API layers.
AuthenticationOAuth 2.0 Device Grant — credentials never touch the server.
Token storageLocal filesystem with restricted permissions.
Rate limitingAutomatic 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.


Documentation

Hosted ServerSSE setup for Claude, Cursor, Windsurf, and more
Usage GuidePractical examples and common workflows
Tools ReferenceAll 29 tools with parameters and response shapes
Per-Tool GuidesDeep-dive into each tool module
SecuritySecurity model, token handling, threat mitigations
DevelopmentLocal setup, architecture, testing, contribution
ChangelogVersion history and migration notes

Development

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
RequirementVersion
Node.js>= 18.0.0
npm>= 8.0.0

Full guide: docs/DEVELOPMENT.md


Contributing

See CONTRIBUTING.md for guidelines.

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

License

MIT — see LICENSE.


Website · Docs · Issues · Changelog

Built by GitScrum

Frequently asked questions

What is io.github.gitscrum-core/mcp-server?

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

How do I install io.github.gitscrum-core/mcp-server?

It runs on your machine. In Claude Code: claude mcp add io-github-gitscrum-core-mcp-server -e 'GITSCRUM_API_URL=<GITSCRUM_API_URL>' -e 'GITSCRUM_TOKEN=<your gitscrum_token>' -- npx -y @gitscrum-studio/mcp-server@1.0.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.gitscrum-core/mcp-server need an API key?

Yes. It expects GITSCRUM_TOKEN, which you set in its configuration.

Is io.github.gitscrum-core/mcp-server open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.gitscrum-core/mcp-server?

It is published by gitscrum-core. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.