A side-by-side look at the Redmine MCP Server and MCP Linear 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 Server for product management work; choose MCP Linear for product management as a local process. You can also run both side by side in one mcpServers block.
REDMINE_URL, REDMINE_API_KEY.getCurrentUser, listProjects, getProject.LINEAR_API_TOKEN, LINEAR_OAUTH_ACCESS_TOKEN.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 45/100 · Fair | 51/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | REDMINE_URLREDMINE_API_KEY | LINEAR_API_TOKENLINEAR_OAUTH_ACCESS_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 147 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 39 | Not listed |
| Full listing | View Redmine MCP Server | View MCP Linear |
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.No tool names declared yet. Check the project README from the listing page.
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.
No confirmed install command for Redmine MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"tacticlaunch-mcp-linear": {
"command": "npx",
"args": [
"-y",
"@tacticlaunch/mcp-linear"
],
"env": {
"LINEAR_API_TOKEN": "YOUR_LINEAR_API_TOKEN_HERE",
"LINEAR_OAUTH_ACCESS_TOKEN": "YOUR_LINEAR_OAUTH_ACCESS_TOKEN_HERE"
}
}
}
}