A side-by-side look at the Targetprocess 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 Targetprocess MCP Server for product management work as a local process; choose MCP Linear for product management as a local process. You can also run both side by side in one mcpServers block.
get_current_releases, get_release_bugs, get_release_features.LINEAR_API_TOKEN, LINEAR_OAUTH_ACCESS_TOKEN.Rows where the two servers differ are marked.
| Spec | T Targetprocess MCP Server | |
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 52/100 · Good | 51/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 | LINEAR_API_TOKENLINEAR_OAUTH_ACCESS_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 8 | 147 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 79 | Not listed |
| Full listing | View Targetprocess MCP Server | View MCP Linear |
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_featurecoveredNo 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.
{
"mcpServers": {
"targetprocess-mcp-server": {
"command": "npx",
"args": [
"-y",
"targetprocess-mcp-server"
]
}
}
}
{
"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"
}
}
}
}