Redmine MCP Stdio vs Gitscrum Core MCP
A side-by-side look at the Redmine MCP Stdio and Gitscrum Core MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Redmine MCP Stdio for product management work as a local process; choose Gitscrum Core MCP for product management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Redmine MCP Stdio when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
REDMINE_URL, REDMINE_API_KEY. - You want tools like
list_issues, get_issue, list_projects.
Choose Gitscrum Core MCP when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You want tools like
task, sprint, workspace.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 53/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | REDMINE_URLREDMINE_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 12 | 29 |
| Full listing | View Redmine MCP Stdio | View Gitscrum Core MCP |
Tools & capabilities
Redmine MCP Stdio tools 12
list_issuesList/filter issues, paginatedget_issueFull details of one issue + comments/history + attachmentslist_projectsAccessible projectsget_projectProject details, versions and memberscreate_issueCreate an issueupdate_issueUpdate issue fieldsadd_commentAdd a note to an issuelog_timeLog a time entry on an issue/projectlist_time_entriesList time entries, filteredlist_enumerationsIDs of trackers/statuses/priorities/activitiessearchFull-text search (issues, wiki, news, …)get_current_userAccount behind the API key (id, login, name)
Gitscrum Core MCP tools 29
task[tasks](docs/tools/tasks.md)sprint[sprints](docs/tools/sprints.md)workspace[projects](docs/tools/projects.md)project[projects](docs/tools/projects.md)time[time-tracking](docs/tools/time-tracking.md)user_story[user-stories](docs/tools/user-stories.md)epic[epics](docs/tools/epics.md)label[labels](docs/tools/labels.md)task_type[task-types](docs/tools/task-types.md)workflow[workflows](docs/tools/workflows.md)discussion[discussions](docs/tools/discussions.md)comment[comments](docs/tools/comments.md)- +17 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Redmine MCP Stdio
{
"mcpServers": {
"andrelaptenok-redmine-mcp-stdio": {
"command": "npx",
"args": [
"-y",
"redmine-mcp-stdio"
],
"env": {
"REDMINE_URL": "YOUR_REDMINE_URL_HERE",
"REDMINE_API_KEY": "YOUR_REDMINE_API_KEY_HERE"
}
}
}
}
Gitscrum Core MCP
{
"mcpServers": {
"mcp-93": {
"command": "npx",
"args": [
"-y",
"@gitscrum-studio/mcp-server"
]
}
}
}
Frequently asked questions
Redmine MCP Stdio is categorized under Product Management and uses a local stdio subprocess. Gitscrum Core MCP belongs to Product Management and uses a local stdio subprocess. Pick Redmine MCP Stdio for product management work and Gitscrum Core MCP for product management.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Redmine MCP Stdio is listed as free. Auth: api key required. Gitscrum Core MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add andrelaptenok-redmine-mcp-stdio and mcp-93 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Redmine MCP Stdio has a quality signal of 53/100 (Good) with 3 views, 0 installs and 0 GitHub stars. Gitscrum Core MCP has 57/100 (Good) with 0 views, 0 installs and 5 GitHub stars.