Casefile vs Redmine MCP Stateless
A side-by-side look at the Casefile and Redmine MCP Stateless MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Casefile for product management work over a hosted endpoint; choose Redmine MCP Stateless for product management over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Casefile when
- You need dedicated capabilities in the Product Management domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
get_task, search_tasks, create_task.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 53/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | MCP_TRANSPORTREDMINE_URLREDMINE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | 32 | 13 |
| Full listing | View Casefile | View Redmine MCP Stateless |
Tools & capabilities
Casefile tools 32
get_taskreturns everything about one task in a single call: card, parent and children, links, computed features, latest summary, open questions, unresolved remarks, its discussions, case index and transition targetssearch_taskssearches tasks by a query-language string, by separate conditions, or by bothcreate_taskcreates a task in `backlog` in an area of its project (`area_required` without one), optionally as a child of a parent taskupdate_taskchanges the given fields of a task; fields left out stay as they aretransitionmoves a task to another status along the fixed transition tableclose_taskcloses a task: files entries, verdicts and the final summary and moves it to `done`, in one transactionmove_taskmoves a task, or each task of a list with an outcome per key, to another project with a reason; its previous key keeps leading to itread_entriesreturns entry bodies of one task's case, with payload, in number orderadd_summaryfiles a summary: the handover note of a case, in four partsadd_entryfiles an entry without payload: a decision, attempt, finding, artifact, remark or noteaskfiles a question to registry participants in a discussion; asked about a task, it opens the discussion and attaches the task in the same callansweranswers a question of a discussion or of a task's case, or closes one still unanswered as `withdrawn` or `replaced` by a later question, with a reason; an answered question cannot be withdrawn- +20 more on the listing page
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
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.
Casefile
{
"mcpServers": {
"casefile": {
"url": "http://localhost:8100/mcp"
}
}
}
Redmine MCP Stateless
{
"mcpServers": {
"daiji-sshr-redmine-mcp-stateless": {
"url": "http://localhost:8000/sse"
}
}
}
Frequently asked questions
Casefile is categorized under Product Management and uses a remote HTTP/SSE transport. Redmine MCP Stateless belongs to Product Management and uses a remote HTTP/SSE transport. Pick Casefile for product management work and Redmine MCP Stateless 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.
Casefile has no declared pricing — check the project's own site. Redmine MCP Stateless is listed as free. Auth: api key required. 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 casefile and daiji-sshr-redmine-mcp-stateless as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Casefile has a quality signal of 53/100 (Good) with 0 views, 0 installs and 6 GitHub stars. Redmine MCP Stateless has 55/100 (Good) with 7 views, 0 installs and 1 GitHub stars.
