Targetprocess MCP Server vs Redmine MCP Stdio
A side-by-side look at the Targetprocess MCP Server and Redmine MCP Stdio MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
Targetprocess MCP ServerProduct Management · Local subprocess (stdio)MCP server for Tartget Process52GoodAuth: not declaredVerdict: choose Targetprocess MCP Server for product management work as a local process; choose Redmine MCP Stdio 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?
TChoose Targetprocess MCP Server when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_current_releases, get_release_bugs, get_release_features.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Targetprocess MCP Server | |
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 52/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | REDMINE_URLREDMINE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 8 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 79 | 12 |
| Full listing | View Targetprocess MCP Server | View Redmine MCP Stdio |
Tools & capabilities
Targetprocess MCP Server tools 79
get_current_releasesget_release_bugsget_release_featuresget_release_user_storiesget_release_user_stories_with_descriptionget_release_open_bugsget_release_open_user_storiesget_feature_contentget_feature_commentsget_feature_user_storiesget_not_covered_user_stories_in_featurecovered- +67 more on the listing page
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)
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.
Targetprocess MCP Server
{
"mcpServers": {
"targetprocess-mcp-server": {
"command": "npx",
"args": [
"-y",
"targetprocess-mcp-server"
]
}
}
}
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"
}
}
}
}
Frequently asked questions
Targetprocess MCP Server is categorized under Product Management and uses a local stdio subprocess. Redmine MCP Stdio belongs to Product Management and uses a local stdio subprocess. Pick Targetprocess MCP Server for product management work and Redmine MCP Stdio 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.
Targetprocess MCP Server has no declared pricing — check the project's own site. Redmine MCP Stdio 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 targetprocess-mcp-server and andrelaptenok-redmine-mcp-stdio as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Targetprocess MCP Server has a quality signal of 52/100 (Good) with 0 views, 0 installs and 8 GitHub stars. Redmine MCP Stdio has 53/100 (Good) with 3 views, 0 installs and 0 GitHub stars.
