A side-by-side look at the Plane MCP Server and Gitscrum Core MCP 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 Gitscrum Core MCP 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.task, sprint, workspace.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 51/100 · Good | 57/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 | 5 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | 29 |
| Full listing | View Plane MCP Server | View Gitscrum Core MCP |
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 retrievetask[tasks](docs/tools/tasks.md)sprint[sprints](docs/tools/sprints.md)workspace[projects](docs/tools/projects.md)project[projects](docs/tools/projects.md)time[time-tracking](docs/tools/time-tracking.md)user_story[user-stories](docs/tools/user-stories.md)epic[epics](docs/tools/epics.md)label[labels](docs/tools/labels.md)task_type[task-types](docs/tools/task-types.md)workflow[workflows](docs/tools/workflows.md)discussion[discussions](docs/tools/discussions.md)comment[comments](docs/tools/comments.md)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 Plane MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"mcp-93": {
"command": "npx",
"args": [
"-y",
"@gitscrum-studio/mcp-server"
]
}
}
}