Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Gitscrum Core MCP

by gitscrum-coreversion 1.0.1i★ –iRuns on your computer
Registry nameio.github.gitscrum-core/mcp-server

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: GITSCRUM_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: GITSCRUM_API_URL, GITSCRUM_TOKEN

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

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

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

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.

Open in VS Code

Or copy the settings yourself

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.

Values you fill in

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

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account gitscrum-core, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 18326 servers in this category
  • Published to the registry more recently than 2% of the other 18326 servers in this category
  • Basic checks equal to or better than 100% of the other 18326 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Gitscrum Core MCP safe?

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.

What keys or codes does it need?

You need to fill in: GITSCRUM_TOKEN

Does it run on my computer or in the cloud?

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

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 9 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Signoff

Alternatives

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

Signoff

by ayuanxx-max

Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.

Runs on your computerUpdated today
Install

README from the maker

Open the README

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.

⚡ Hosted (Recommended)

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"] } } }

</details>

VS Code / Cursor

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

{

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

</details>
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 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

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

Ask PopNx