Server Everything vs P4plan MCP
A side-by-side look at the Server Everything 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 Server Everything for other tools and integrations 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 Server Everything when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
echo, get-annotated-message, get-env.
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 | Other Tools and Integrations | Product Management |
| Quality signal | 73/100 · Great | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | P4PLAN_API_AUTH_TOKENP4PLAN_API_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 91,550 | 4 |
| Directory activity | 10 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 16 | 2 |
| Full listing | View Server Everything | View P4plan MCP |
Tools & capabilities
Server Everything tools 16
echoEchoes back the input stringget-annotated-messageDemonstrates how annotations can be used to provide metadata about content.get-envReturns all environment variables, helpful for debugging MCP server configurationget-header-paramsReturns its region argument and the Mcp-Param-Region HTTP header it arrived in. Demonstrates x-mcp-header (a 2026-07-28 Streamable HTTP client mirrors the argument into the header) and JSON Schema 2020-12 input and output schemas.get-resource-linksReturns up to ten resource links that reference different types of resourcesget-resource-referenceReturns a resource reference that can be used by MCP clientsget-structured-contentReturns structured content along with an output schema for client data validationget-sumReturns the sum of two numbersget-tiny-imageReturns a tiny MCP logo image.gzip-file-as-resourceCompresses a single file using gzip compression. Depending upon the selected output type, returns either the compressed data as a gzipped resource or a resource link, allowing it to be downloaded in a subsequent request: during the current session for a 2025-era client, or for ten minutes at a minted URI on protocol version 2026-07-28.trigger-list-changedSends a notifications/<list>/list_changed for the tool, prompt or resource list. On protocol version 2026-07-28 it is delivered on each subscriptions/listen stream that asked for that list; a 2025-era client receives it unsolicited.trigger-log-messagesSends one log message at each logging level during the call. On protocol version 2026-07-28 only the messages at or above the level the request names in _meta (io.modelcontextprotocol/logLevel) are sent, and none if it names no level; a 2025-era client gets those at or above the level it set with logging/setLevel. Deprecated: logging is deprecated as of protocol version 2026-07-28.- +4 more on 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.
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
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
Server Everything is categorized under Other Tools and Integrations and uses a local stdio subprocess. P4plan MCP belongs to Product Management and uses a local stdio subprocess. Pick Server Everything for other tools and integrations 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.
Server Everything is listed as free. Auth: no auth required. 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 modelcontextprotocol-server-everything and p4plan-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Server Everything has a quality signal of 73/100 (Great) with 10 views, 0 installs and 91,550 GitHub stars. P4plan MCP has 56/100 (Good) with 2 views, 0 installs and 4 GitHub stars.