1. Conduid
  2. Developer Tools
  3. server
MCP server · Developer Tools

server

Model Context Protocol server for GitScrum - Enable AI assistants to manage tasks, track time, run sprints, and handle client relationships through natural language

Unclaimed devtools
39Low

Scored 4 months ago · breakdown

About server

server is an MCP server published by git+gitscrum-core in the Developer Tools category: model Context Protocol server for GitScrum - Enable AI assistants to manage tasks, track time, run sprints, and handle client relationships through natural language. It has been installed 0 times through Conduid.

Install

Install
npx @gitscrum-studio/mcp-server
Claude Code
claude mcp add server-gitgitsc -- npx -y @gitscrum-studio/mcp-server
npx
npx -y @gitscrum-studio/mcp-server

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about server

Powered by Claude · Grounded in docs

I know everything about server. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

⚡ 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

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

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

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

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


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 security@gitscrum.com.


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

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


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.


README mirrored from the source repository 4 months ago. The original is authoritative.

Questions

About server

How do I install server?

Run npx @gitscrum-studio/mcp-server, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is server safe to use with an AI agent?

Its trust score is 39 out of 100 (low). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is server still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.