Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.gitscrum/mcp

NPM · @GITSCRUM-STUDIO/MCP-SERVER

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

0 this week 85 Trust /100

Last scanned (9 hours ago)

Scores higher than 83% of npm servers

Category Project Management

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency47
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 267 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 6363 tokens (~205/item across 31 items; 29 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 29 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 31 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 2 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 27 Oct 26 0
    • Stability: 0.97 → pass security
  • 26 Oct 26 0
    • Stability: pass → 0.97 functional
  • 20 Oct 26 0
    • Stability: 0.97 → pass security
  • 19 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +3
    • Stability: 0.87 → pass security
    • Security disclosure: unverified → pass ▲ functional
  • 16 Oct 26 −1
    • Security disclosure: pass → unverified ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 7 Nov 2026 · Analysed npm/@gitscrum-studio/mcp-server@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 29 exposed · ~6,317 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
activity ~215

Activity feed & history. Actions: feed, user_feed, notifications, activities, task_workflow. Workflow: - 'feed': no params needed (current user's activity feed) - 'user_feed': requires username (activity feed for specific user) - 'notifications': no params needed (notification feed) - 'activities': requires from_context (company, project, sprint). Uses company_slug/project_slug/sprint_slug - 'task_workflow': requires task_uuid (workflow/status change history for a task)

NameTypeReqDescription
actionstringyesWhich operation to perform
company_slugstring–Workspace identifier (for activities)
from_contextstring–Context filter for activities action
project_slugstring–Project identifier (for activities)
sprint_slugstring–Sprint slug (for activities with sprint context)
task_uuidstring–Task UUID for task_workflow action
usernamestring–Username for user_feed action
uuidstring–Entity UUID for activities by specific entity

No output schema declared.

No examples provided.

analytics ~227

Analytics. Reports: pulse (health), risks, flow (WIP), age, activity, overview, health, blockers, command_center, time_entries. All reports require company_slug (get from 'workspace' tool action 'list'). overview/health/blockers/command_center/time_entries are Manager Dashboard reports.

NameTypeReqDescription
company_slugstringyesWorkspace slug (ALWAYS REQUIRED)
daysnumber–For 'flow' report: number of days (default: 30, max: 90)
filterstring–For 'risks' report: filter by risk type (default: all)
periodstring–For 'pulse' report: time period (default: this-week)
reportstringyesWhich analytics report to get (REQUIRED)
severitystring–For 'risks' report: filter by severity (default: all)
time_filterstring–For 'time_entries' report: filter type (default: today)
viewstring–For 'pulse' report: filter view (default: all)

No output schema declared.

No examples provided.

auth_complete ~32

Complete login after browser authorization.

NameTypeReqDescription
device_codestringyesThe device_code returned from auth_login (REQUIRED)

No output schema declared.

No examples provided.

auth_login ~19

Start login. Returns URL and code for browser authorization.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

auth_logout ~13

Logout and clear token.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

auth_status ~12

Check authentication status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

budget ~230

Project budget tracking. Actions: projects_at_risk, overview, consumption, burn_down, alerts, events. Workflow: - 'projects_at_risk': requires company_slug (shows projects exceeding budget across workspace) - 'overview': requires project_uuid (budget overview with optional date filters) - 'consumption': requires project_uuid (current budget consumption) - 'burn_down': requires project_uuid (budget burn-down chart data) - 'alerts': requires project_uuid (budget threshold alerts) - 'events': requires project_uuid (budget event log)

NameTypeReqDescription
actionstringyesWhich operation to perform
company_slugstring–Workspace identifier. Required for: projects_at_risk
end_datestring–End date filter YYYY-MM-DD (optional for overview/burn_down)
limitnumber–Max results for events (default 20, max 100)
project_uuidstring–Project UUID. Required for: overview, consumption, burn_down, alerts, events
start_datestring–Start date filter YYYY-MM-DD (optional for overview/burn_down)

No output schema declared.

No examples provided.

client ~233

Client management. Actions: list, get, stats, create, update. All actions require company_slug. 'get'/'stats'/'update' require uuid (from 'list' response).

NameTypeReqDescription
actionstringyesWhich operation to perform
addressstring–Street address (optional)
address_line_2string–Address line 2 (optional)
citystring–City name (optional)
company_slugstringyesWorkspace identifier (always required)
countrystring–Country name (optional)
emailstring–Email address (optional)
namestring–Client name text. Required when creating a new client.
notesstring–Internal notes about client (optional)
phonestring–Phone number (optional)
postcodestring–Postal/ZIP code (optional)
uuidstring–Existing client's unique ID. Only for: get, stats, update. NOT for create.
vat_numberstring–VAT/Tax ID (optional)
websitestring–Website URL (optional)

No output schema declared.

No examples provided.

clientflow_cross_workspace ~108

Cross-workspace ClientFlow overview. Reports: invoices, proposals, clients, change_requests. Aggregates data across ALL workspaces owned by the user. No company_slug needed. Returns stats, per-workspace breakdown, and paginated list. Requires Pro subscription.

NameTypeReqDescription
pagenumber–Page number (default 1)
per_pagenumber–Results per page (1-100, default 50)
reportstringyesWhich cross-workspace report to get

No output schema declared.

No examples provided.

clientflow_dashboard ~72

CRM dashboard. Reports: overview, revenue, at_risk, pending, health, insights, leaderboard, analytics. All reports require company_slug (get from 'workspace' tool action 'list').

NameTypeReqDescription
company_slugstringyesWorkspace identifier (always required)
reportstringyesWhich report to generate

No output schema declared.

No examples provided.

comment ~170

Task comments. Actions: list, add, update. Workflow: - 'list'/'add': requires task_uuid (get from 'task' tool) + company_slug + project_slug - 'update': requires comment_id (get from 'list' response) + text

NameTypeReqDescription
actionstringyesWhich operation to perform
comment_idnumber–Existing comment's ID number. Only for: update
company_slugstring–Workspace identifier. Required for: list, add
project_slugstring–Project identifier. Required for: list, add
task_uuidstring–Task's unique ID. Required for: list, add
textstring–Comment text content. This is what you want to write. Required for: add, update

No output schema declared.

No examples provided.

discussion ~381

Discussions & channels. Actions: all, channels, channel, messages, send, search, unread, mark_read, create_channel, update_channel. Workflow: - 'all': no params needed (returns all discussions across workspaces) - 'channels': requires company_slug + project_slug (list channels in a project) - 'channel': requires channel_uuid (get single channel details) - 'messages': requires channel_uuid (get messages, supports cursor pagination) - 'send': requires channel_uuid + content (send a message) - 'search': requires channel_uuid + q (search messages in channel) - 'unread': requires company_slug + project_slug (unread count) - 'mark_read': requires channel_uuid (mark channel as read) - 'create_channel': requires name + company_slug + project_slug - 'update_channel': requires channel_uuid + name or description

NameTypeReqDescription
actionstringyesWhich operation to perform
after_idstring–Cursor for newer messages (optional for messages)
before_idstring–Cursor for older messages (optional for messages)
channel_uuidstring–Channel UUID for: channel, messages, send, search, mark_read, update_channel
company_slugstring–Workspace identifier
contentstring–Message text for send action
descriptionstring–Channel description (optional)
include_archivedboolean–Include archived channels (optional for channels)
is_privateboolean–Channel visibility (optional for create_channel)
limitnumber–Max results (optional)
namestring–Channel name for create_channel/update_channel
parent_idstring–Parent message ID for thread replies (optional for send)
project_slugstring–Project identifier
qstring–Search query for search action

No output schema declared.

No examples provided.

epic ~184

Epics. Actions: list, create, update. Workflow: - 'list': requires company_slug + project_slug (returns epics with their uuid) - 'create': requires title + company_slug + project_slug - 'update': requires epic_uuid (from 'list' response) + company_slug + project_slug

NameTypeReqDescription
actionstringyesWhich operation to perform
colorstring–Color hex code without # e.g. 'FF5733' (optional)
company_slugstringyesWorkspace identifier (always required)
descriptionstring–Epic description in markdown (optional)
epic_uuidstring–Existing epic's unique ID. Only for: update. NOT for create.
project_slugstringyesProject identifier (always required)
titlestring–Epic title/name text. Required when creating a new epic.

No output schema declared.

No examples provided.

invoice ~259

Invoice management. Actions: list, get, stats, create, update, issue, send, mark_paid. Workflow: - 'create': requires company_slug + contact_company_uuid (client UUID from 'client' tool 'list') - 'get'/'update'/'issue'/'send'/'mark_paid': requires uuid (invoice UUID from 'list' response) - Flow: create → issue → send → mark_paid

NameTypeReqDescription
actionstringyesWhich operation to perform
client_uuidstring–Filter by client (optional)
company_slugstringyesWorkspace identifier (always required)
contact_company_uuidstring–Client ID to invoice. Required for creating new invoice.
currencystring–3-letter ISO currency code: USD, EUR, BRL (optional)
due_datestring–Due date in YYYY-MM-DD format, e.g. '2025-12-31' (optional)
notesstring–Invoice notes (optional)
statusstring–Filter: draft, sent, paid, overdue (optional)
uuidstring–Existing invoice's unique ID. Only for: get, update, issue, send, mark_paid. NOT for create.

No output schema declared.

No examples provided.

label ~227

Labels. Actions: list, create, update, attach, detach, toggle. Workflow: - 'list': requires company_slug (returns all workspace labels with their slug/ID) - 'create': requires company_slug + title + color - 'toggle'/'attach'/'detach': requires label_slug (from 'list') + task_uuid (from 'task' tool) + project_slug - 'update': requires label_slug (from 'list') + company_slug

NameTypeReqDescription
actionstringyesWhich operation to perform
colorstring–Hex color code without # e.g. 'FF5733'. Required for: create
company_slugstringyesWorkspace identifier (always required)
label_slugstring–Existing label's identifier. Required for: update, attach, detach, toggle
project_slugstring–Project identifier. Required for: attach, detach, toggle
task_uuidstring–Task's unique ID. Required for: toggle
titlestring–Label name text. Required when creating a new label.

No output schema declared.

No examples provided.

note ~243

Notes. Actions: list, get, create, update, share, revisions. company_slug is optional (auto-inferred from user). 'get'/'update'/'share'/'revisions' require uuid (from 'list' response).

NameTypeReqDescription
actionstringyesWhich operation to perform
colorstring–Color code: gray, blue, red, green, yellow, purple, coral, amber, sky, lime (or hex without #)
company_slugstring–Workspace identifier (optional - auto-detected from user if not provided)
contentstring–The note body text you want to save (Markdown). This is where you put the actual content! Required for action=create.
folder_uuidstring–Folder ID to organize note into (optional)
searchstring–Search term to filter notes (only for list action)
titlestring–Note title/heading text. Required for action=create.
uuidstring–⚠️ ONLY for existing notes! This is the note's database ID. NEVER use for action=create. Use ONLY for: get, update, share, revisions.

No output schema declared.

No examples provided.

note_folder ~142

Note folders. Actions: list, create, update, move. 'move' requires note_uuid (from 'note' tool 'list') and folder_uuid (from 'list' response).

NameTypeReqDescription
actionstringyesWhich operation to perform
company_slugstringyesWorkspace identifier (always required)
folder_uuidstring–Target folder ID to move note into. Omit to unfile note.
namestring–Folder name text. Required for create and update.
note_uuidstring–Note ID to move. Required for move action.
uuidstring–Existing folder's unique ID. Only for update action.

No output schema declared.

No examples provided.

project ~290

Project management. Actions: create, find (by name), list, get, stats, tasks, workflows, types, efforts, labels, members. Workflow: - 'list': requires company_slug (from 'workspace' tool). Returns projects with their project_slug. - 'find': search by name, returns project_slug + company_slug - 'workflows'/'types'/'efforts'/'labels': returns IDs used by 'task' tool for create/update - 'members': returns project assignees (name, username, avatar). Use to know who can be assigned tasks - 'create': requires company_slug + name

NameTypeReqDescription
actionstringyesWhich operation to perform
client_uuidstring–Client UUID to associate project with. Optional for: create
company_slugstring–Workspace identifier. Required for: create, list, get, stats, tasks, etc. Optional for: find
descriptionstring–Project description. Optional for: create
namestring–Project name. Required for: create, find
project_slugstring–Project identifier. Required for: get, stats, tasks, workflows, types, efforts, labels, members
statusstring–Filter projects by status. Optional for: list
visibilitystring–Project visibility (default: public). Optional for: create

No output schema declared.

No examples provided.

proposal ~293

Proposal management. Actions: list, get, stats, create, update, send, approve, reject, convert. Workflow: - 'create': requires company_slug + title. Optional: contact_company_uuid (client from 'client' tool) - 'get'/'update'/'send'/'approve'/'reject'/'convert': requires uuid (from 'list' response) - Flow: create → send → approve/reject. 'convert' turns approved proposal into a project.

NameTypeReqDescription
actionstringyesWhich operation to perform
client_uuidstring–Filter by client (optional)
company_slugstringyesWorkspace identifier (always required)
contact_company_uuidstring–Client ID (optional)
contentstring–Proposal body in Markdown (optional)
currencystring–Currency: USD, EUR, BRL (optional)
reasonstring–Rejection reason (for reject action)
statusstring–Filter: draft, sent, approved, rejected (optional)
titlestring–Proposal title text. Required when creating a new proposal.
total_amountnumber–Total value amount (optional)
uuidstring–Existing proposal's unique ID. Only for: get, update, send, approve, reject, convert. NOT for create.
valid_untilstring–Expiration date YYYY-MM-DD (optional)

No output schema declared.

No examples provided.

search ~103

Search across workspaces, projects, tasks, sprints, wiki, notes by name. Use to discover slugs and UUIDs needed by other tools. Results include entity type, name, and identifiers.

NameTypeReqDescription
categoriesstring–Filter: workspaces, tasks, projects, user_stories, sprints, wiki, notes
limitnumber–Results per category (default: 5)
querystringyesSearch text (min 2 chars)

No output schema declared.

No examples provided.

sprint ~410

Sprint management. Actions: list, all, get, kpis, stats, reports, progress, metrics, create, update. Workflow: - 'list': requires company_slug + project_slug (returns sprints with their slug) - 'all': no params needed (returns all sprints across workspaces) - 'get'/'kpis'/'stats'/'progress'/'metrics': requires slug (sprint slug from 'list' response) + company_slug + project_slug - 'reports': requires slug + company_slug + project_slug. Optional: resource (burndown, burnup, performance, types, efforts) - 'create': requires title + company_slug + project_slug. Dates default to today → +7 days - 'update': requires slug + company_slug + project_slug

NameTypeReqDescription
actionstringyesWhich operation to perform
close_on_finishboolean–Auto-close when end date reached (optional)
colorstring–Hex color without # e.g. 'FF5733' (optional)
company_slugstring–Workspace identifier. Required for: list, get, kpis, create, update, delete
date_finishstring–End date YYYY-MM-DD (default: today + 7 days)
date_startstring–Start date YYYY-MM-DD (default: today)
descriptionstring–Sprint description in markdown (optional)
is_privateboolean–Sprint visibility (optional)
project_slugstring–Project identifier. Required for: list, get, kpis, create, update, delete
resourcestring–For 'reports': filter to single chart (burndown, burnup, performance, types, efforts, member_distribution, task_type_distribution)
slugstring–Existing sprint's slug. Required for: get, kpis, update, delete. NOT for create
titlestring–Sprint name. Required for: create

No output schema declared.

No examples provided.

standup ~135

Standup reports. Actions: summary, completed, blockers, team, stuck, digest, contributors. All actions require company_slug (get from 'workspace' tool action 'list'). Optional: project_slug to filter by project, date in YYYY-MM-DD format.

NameTypeReqDescription
actionstringyesWhat standup info to get
company_slugstringyesWorkspace identifier (always required)
datestring–Date in YYYY-MM-DD format (default: yesterday)
periodstring–Time period for 'contributors' action (default: month)
project_slugstring–Filter to specific project (optional)

No output schema declared.

No examples provided.

task ~830

Task management. Actions: my, today, notifications, get, create, update, complete, subtasks, filter, by_code, duplicate, move. Workflow: - 'my' and 'today': no extra params needed, returns user's tasks - 'create': requires company_slug + project_slug + title. ALL optional fields (sprint_slug, user_story_slug, column, type_id, effort_id, usernames, etc.) can be set in ONE call - 'update': requires uuid + company_slug + project_slug. Accepts same optional fields as create - 'get'/'complete'/'subtasks': requires uuid (task UUID from any task listing) - 'filter': requires company_slug + project_slug, supports many filter params - 'by_code': requires task_code (e.g. 'PROJ-123') + company_slug + project_slug - 'duplicate': requires uuid + company_slug + project_slug - 'move': requires uuid + company_slug + project_slug + new_project_slug + new_workflow_id

NameTypeReqDescription
actionstringyesWhich operation to perform
closed_atstring–Filter: Closed date range YYYY-MM-DD=YYYY-MM-DD
columnstring–Kanban column name e.g. 'Done', 'In Progress'. Easier than workflow_id - MCP resolves the ID
company_slugstring–Workspace identifier. Required for: create, update, filter
created_atstring–Filter: Created date range YYYY-MM-DD=YYYY-MM-DD
descriptionstring–Task description in markdown (optional)
due_datestring–Deadline in YYYY-MM-DD format, e.g. '2025-12-31'
effortstring–Filter: Priority/effort title
effort_idnumber–Priority level ID (get from project action=efforts)
estimated_minutesnumber–Time estimate in minutes (e.g. 60 for 1 hour)
is_archivedboolean–Archive task (for update/filter)
is_blockerboolean–Mark task as blocker (for create/update/filter)
is_bugboolean–Mark task as bug (for create/update)
label_idsarray–Array of label IDs to attach
labelsstring–Filter: Comma-separated label titles
new_project_slugstring–Target project for move action
new_workflow_idnumber–Target workflow/column ID for move action
parent_idstring–Parent task UUID to create as subtask
per_pagenumber–Number of results (1-100, default 50)
project_slugstring–Project identifier. Required for: create, update, filter
sprintstring–Filter: Sprint slug
sprint_slugstring–Sprint identifier to add task to
start_datestring–Start date in YYYY-MM-DD format
statusstring–Filter: Status
task_codestring–Task code for by_code action (e.g. 'PROJ-123')
task_uuidstring–Alias for uuid (from context)
titlestring–Task name/title text. Required when creating a new task.
typestring–Filter: Task type title
type_idnumber–Task type ID (get from project action=types)
unassignedboolean–Filter: Only unassigned tasks
user_storystring–Filter: User story slug
user_story_slugstring–User story identifier to link task to
usernamesarray–Array of usernames to assign
usersstring–Filter: Comma-separated usernames
uuidstring–Task UUID. For: get, update, complete, subtasks
workflowstring–Filter: Kanban column title
workflow_idnumber–Kanban column ID. Use this OR column name

No output schema declared.

No examples provided.

task_type ~240

Task types (Bug, Feature, etc). Actions: list, create, update, assign. Workflow: - 'list': requires company_slug + project_slug (returns types with their ID) - 'create': requires title + color + company_slug + project_slug - 'update': requires type_id (from 'list' response) + company_slug + project_slug - 'assign': requires type_id (from 'list') + task_uuid (from 'task' tool) + company_slug + project_slug

NameTypeReqDescription
actionstringyesOperation to perform (REQUIRED)
colorstring–6-character hex code without # (e.g. 'FF5733') (REQUIRED for: create)
company_slugstringyesWorkspace slug (ALWAYS REQUIRED)
project_slugstringyesProject slug (ALWAYS REQUIRED)
task_uuidstring–Task UUID (REQUIRED for: assign)
titlestring–Type name e.g. 'Bug', 'Feature' (REQUIRED for: create)
type_idnumber–Task type ID (REQUIRED for: update, assign)

No output schema declared.

No examples provided.

time ~409

Time tracking. Actions: active, start, stop, logs, analytics, team, reports, productivity, timeline. Workflow: 1. Use 'active' first to check if there is already a running timer 2. To start: get the task_uuid from 'task' tool (action: my, today, or filter), then call 'start' with task_uuid 3. To stop: get time_tracking_id from 'active' response, then call 'stop' 4. 'logs' shows time entries for a project 5. 'analytics'/'team'/'reports'/'productivity'/'timeline': requires company_slug. Optional: project_slug, period 'active' and 'logs' require company_slug (auto-resolved if omitted). 'start' requires task_uuid (ask user which task if not specified). 'stop' requires time_tracking_id (get from 'active' response). Period options: today, yesterday, last-7-days, last-14-days, last-15-days, this-month, last-month, last-30-days

NameTypeReqDescription
actionstringyesWhich operation to perform
company_slugstring–Workspace identifier. Required for: active, logs (auto-resolved if omitted)
descriptionstring–What you're working on (optional note for start)
hourly_ratenumber–For 'reports' action: hourly rate for cost calculations
periodstring–Time period for analytics: today, yesterday, last-7-days, last-14-days, this-month, last-month, last-30-days
project_slugstring–Project identifier. Required for: logs
report_typestring–For 'reports' action: report type (default: summary)
task_uuidstring–Task's unique ID to track time on. Required for: start
time_tracking_idstring–Active timer's ID (get from 'active' action). Required for: stop

No output schema declared.

No examples provided.

user_story ~286

User stories. Actions: list, all, get, create, update. Workflow: - 'list': requires company_slug + project_slug (returns stories with their slug) - 'all': no params needed (returns all user stories across workspaces) - 'get': requires slug (from 'list' response) + company_slug + project_slug - 'create': requires title + company_slug + project_slug - 'update': requires slug (from 'list' response) + company_slug + project_slug

NameTypeReqDescription
acceptance_criteriastring–Definition of done - what must be true for story to be complete (optional)
actionstringyesWhich operation to perform
additional_informationstring–Story details/context in markdown (optional for create)
company_slugstringyesWorkspace identifier (always required)
epic_uuidstring–Epic UUID to associate story with (from 'epic' tool 'list'). Optional for create/update
project_slugstringyesProject identifier (always required)
slugstring–Existing story's unique identifier. Only for: get, update. NOT for create.
titlestring–Story title text. Required when creating a new story.
user_story_priority_idnumber–Priority ID (from 'project' action 'efforts'). Optional - auto-defaults on create

No output schema declared.

No examples provided.

wiki ~217

Wiki pages. Actions: list, get, create, update, search. All actions require company_slug + project_slug. 'get'/'update' require uuid (from 'list' response). 'search' requires q (search query, min 2 chars).

NameTypeReqDescription
actionstringyesWhich operation to perform
company_slugstringyesWorkspace identifier (always required)
contentstring–Page body text in Markdown. This is the actual content to save. Required for create.
limitnumber–Max results for search (default 20, max 50)
parent_uuidstring–Parent page ID for nested pages (optional)
project_slugstringyesProject identifier (always required)
qstring–Search query (min 2 chars). Required for search action.
titlestring–Page title/heading text. Required when creating a new page.
uuidstring–Existing page's unique ID. Only for: get, update. NOT for create.

No output schema declared.

No examples provided.

workflow ~240

Manage Kanban board columns. Actions: create, update. Workflow: - To see existing columns: use 'project' tool with action 'workflows' - 'create': requires project_slug + title. Optional: color, status (todo/in progress/done) - 'update': requires workflow_id (from 'project' action 'workflows' response). Optional: title, color, position, status

NameTypeReqDescription
actionstringyesAction: create (new column), update (modify existing)
colorstring–Hex code without # e.g. '58A6FF'
company_slugstring–Workspace identifier (optional if project_slug unique)
positionnumber–[update] Board position (1 = leftmost)
project_slugstring–Project identifier
statusstring–Column type: 'todo'/'backlog', 'in progress'/'doing', 'done'/'closed'
titlestring–Column name e.g. 'Backlog', 'In Review', 'Done'
workflow_idnumber–[update] Column ID (from project action 'workflows')

No output schema declared.

No examples provided.

workspace ~97

Workspace management. Actions: list, find (by name), get, stats. This is the starting point. Use 'list' to get all workspaces and their company_slug. company_slug is needed by most other tools.

NameTypeReqDescription
actionstringyesWhich operation to perform
company_slugstring–Workspace identifier. Required for: get, stats
namestring–Workspace name to search for. Required for: find

No output schema declared.

No examples provided.

Install

How do I install the com.gitscrum/mcp server?

com.gitscrum/mcp runs locally as an npm package, launched with npx -y @gitscrum-studio/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @gitscrum-studio/mcp-server

# add to Claude Code
claude mcp add com-gitscrum-mcp -- npx -y @gitscrum-studio/mcp-server
Common questions

What is the com.gitscrum/mcp server?

com.gitscrum/mcp is listed in the public MCP registry as com.gitscrum/mcp. MCP server for GitScrum, manage tasks, sprints, time tracking, and client workflows via AI. This page covers its npm package (@gitscrum-studio/mcp-server).

Is the com.gitscrum/mcp server safe to use?

com.gitscrum/mcp scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 7 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.gitscrum/mcp server expose?

com.gitscrum/mcp exposes 29 tools: auth_login, auth_complete, auth_status, auth_logout, task, and 24 more. Their descriptions and schemas cost roughly 6,317 tokens of context every time the server is loaded.

Is the com.gitscrum/mcp server still maintained?

com.gitscrum/mcp is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the com.gitscrum/mcp server under?

com.gitscrum/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the com.gitscrum/mcp server?

VerifyMCP ran 16 checks on com.gitscrum/mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.