Redmine MCP Stateless vs Redmine MCP Server
A side-by-side look at the Redmine MCP Stateless and Redmine MCP Server 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 Stateless for product management work over a hosted endpoint; choose Redmine MCP Server for product management. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Redmine MCP Stateless when
- You need dedicated capabilities in the Product Management domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
MCP_TRANSPORT, REDMINE_URL, REDMINE_API_KEY. - You want tools like
list_issues, get_issue, create_issue.
Choose Redmine MCP Server when
- You need dedicated capabilities in the Product Management domain.
- You have the keys it needs:
REDMINE_URL, REDMINE_API_KEY. - You want tools like
getCurrentUser, listProjects, getProject.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 55/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | MCP_TRANSPORTREDMINE_URLREDMINE_API_KEY | REDMINE_URLREDMINE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 7 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 13 | 39 |
| Full listing | View Redmine MCP Stateless | View Redmine MCP Server |
Tools & capabilities
Redmine MCP Stateless tools 13
list_issuesList issues with optional filters (project, status, assignee)get_issueIssue details including all comments and attachmentscreate_issueCreate a new issueupdate_issueUpdate an issue or add a commentupdate_journalEdit an existing comment (requires Redmine 5.0+)list_issues_with_journalsList issues with all comments — useful for per-assignee progress reviewsearch_issues_fullFull-text search across subject, description, and commentslist_projectsList all projectsget_projectProject detailslist_statusesAvailable issue statuseslist_trackersAvailable trackerslist_prioritiesAvailable priorities- +1 more on the listing page
Redmine MCP Server tools 39
getCurrentUserCurrent user: ID, login, groups, projects. Useful for "my issues" filteringlistProjectsList of all accessible projectsgetProjectProject details: trackers, modules, descriptionlistProjectMembersProject members with roleslistVersionsProject versions (milestones)listIssuesIssue list with filters: project, status, tracker, assignee, priority, version, saved query, custom fields (`customFieldFilters` in `cf_<id>=value` format), sortingsearchIssuesFull-text issue search with detailed resultsgetIssueIssue details: description, status, assignee, dates, notes, relations, custom fields, attachments, linked revisions (`changesets`). Parameters: `issueId`, `focus` (`default`, `implementation`, `timeline`, `full`; optional)getIssueJournalA single complete issue journal note/event without response compression. Parameters: `issueId`, `journalIdgetMyIssuesIssues of the current user. Parameters: `projectId`, `statusId`, `sort`, `limit`, `offsetgetIssueTreeParent chain and subtasks. `root` and `ancestors` keep the `Issue` JSON shape but contain compact context; call `getIssue` for full details or relations. Parameters: `issueId`, `depth` (default 2, max 5)getIssueHistoryCreation and every journal event, with status intervals. Long text is shortened; `journalId` identifies the full entry for `getIssueJournal`. Follow `nextOffset` with the optional `offset` parameter until it is absent.- +27 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 Stateless
{
"mcpServers": {
"daiji-sshr-redmine-mcp-stateless": {
"url": "http://localhost:8000/sse"
}
}
}
Redmine MCP Server
No confirmed install command for Redmine MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Redmine MCP Stateless is categorized under Product Management and uses a remote HTTP/SSE transport. Redmine MCP Server belongs to Product Management and uses an install path we have not confirmed yet. Pick Redmine MCP Stateless for product management work and Redmine MCP Server 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 Server has no confirmed install command yet — follow its own setup instructions.
Redmine MCP Stateless is listed as free. Auth: api key required. Redmine MCP Server 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 daiji-sshr-redmine-mcp-stateless and redmine-mcp-server-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Redmine MCP Stateless has a quality signal of 55/100 (Good) with 7 views, 0 installs and 1 GitHub stars. Redmine MCP Server has 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
