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