Ithura MCP vs P4plan MCP
A side-by-side look at the Ithura MCP and P4plan MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ithura MCP for product management work as a local process; choose P4plan MCP for product management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ithura MCP when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ITHURA_API_KEY, ITHURA_WORKSPACE_SLUG, ITHURA_API_URL.
Choose P4plan MCP when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
P4PLAN_API_AUTH_TOKEN, P4PLAN_API_URL. - You want tools like
Parameters, Types.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 36/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | ITHURA_API_KEYITHURA_WORKSPACE_SLUGITHURA_API_URL | P4PLAN_API_AUTH_TOKENP4PLAN_API_URL |
Tools & capabilities
Ithura MCP tools
No tool names declared yet. Check the project README from the listing page.
P4plan MCP tools 2
Parameters`projectId`Types`backlog_task`, `bug`, `scheduled_task`, `sprint`, `release`, `sprint_task`
Ready-to-paste client configs
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.
Ithura MCP
{
"mcpServers": {
"mcp-102": {
"command": "npx",
"args": [
"-y",
"ithura-mcp"
],
"env": {
"ITHURA_API_KEY": "YOUR_ITHURA_API_KEY_HERE",
"ITHURA_WORKSPACE_SLUG": "YOUR_ITHURA_WORKSPACE_SLUG_HERE",
"ITHURA_API_URL": "YOUR_ITHURA_API_URL_HERE"
}
}
}
}
P4plan MCP
{
"mcpServers": {
"p4plan-mcp": {
"command": "npx",
"args": [
"-y",
"@perforce/p4plan-mcp"
],
"env": {
"P4PLAN_API_AUTH_TOKEN": "YOUR_P4PLAN_API_AUTH_TOKEN_HERE",
"P4PLAN_API_URL": "YOUR_P4PLAN_API_URL_HERE"
}
}
}
}
Frequently asked questions
Ithura MCP is categorized under Product Management and uses a local stdio subprocess. P4plan MCP belongs to Product Management and uses a local stdio subprocess. Pick Ithura MCP for product management work and P4plan MCP for product management.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Ithura MCP has no declared pricing — check the project's own site. P4plan MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-102 and p4plan-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ithura MCP has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. P4plan MCP has 56/100 (Good) with 2 views, 0 installs and 4 GitHub stars.