A side-by-side look at the MCP Taiga and Plane 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 MCP Taiga for product management work as a local process; choose Plane MCP Server for product management. You can also run both side by side in one mcpServers block.
projects, work, sprints.PLANE_API_KEY, PLANE_WORKSPACE_SLUG.project_id, name, description_html.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 56/100 · Good | 51/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | PLANE_API_KEYPLANE_WORKSPACE_SLUG |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 40 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 6 | 4 |
| Full listing | View MCP Taiga | View Plane MCP Server |
projectsproject` accepts an ID or slugworktype`, `project`, `item`, `subject`, `itemssprintsproject`, `sprint`, `name`, `start`, `finishcommentstype`, `item`, `text`, `commentIdattachmentstype`, `item`, `attachmentId`, `filePath` or `fileContent`, `savePathwikiproject`, `page`, `content`, `watchproject_idID of the project to retrievenameTitle of the issuedescription_htmlHTML description of the issue (required by Plane API)issue_idID of the issue to retrievePaste 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": {
"negoro26-mcp-taiga": {
"command": "npx",
"args": [
"-y",
"mcp-taiga"
]
}
}
}
No confirmed install command for Plane MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.