A side-by-side look at the Productplan MCP Server and Revelica MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Productplan MCP Server for product management work; choose Revelica for product management over a hosted endpoint. You can also run both side by side in one mcpServers block.
PRODUCTPLAN_API_TOKEN.query, read, create.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 33/100 · Emerging | 52/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | PRODUCTPLAN_API_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 6 |
| Full listing | View Productplan MCP Server | View Revelica |
No tool names declared yet. Check the project README from the listing page.
querySearch or filter the workspace by criteria. Returns ranked matches, plus the schema template when `artifact_type` is set.readRead a single artifact or entity in full by id, or navigate to a subtree with a dotted field `path`.createCreate new artifacts or entities. Content validated against registered schemas.updateApply partial field-level updates via dot-path notation.load_skillLoad a server skill's instructions, its readiness and a summary of the records it starts from. This does not itself execute a playbook.list_skillsList the skills you can load, with each one's name, description and any required inputs.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 Productplan MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"revelica": {
"url": "https://api.revelica.com/mcp"
}
}
}