PRIMAMCP vs Server Everything
A side-by-side look at the PRIMAMCP and Server Everything MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose PRIMAMCP for legal work as a local process; choose Server Everything for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose PRIMAMCP when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Other Tools and Integrations |
| Quality signal | 45/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11 | 91,486 |
| Directory activity | 0 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View PRIMAMCP | View Server Everything |
Tools & capabilities
PRIMAMCP tools
No tool names declared yet. Check the project README from the listing page.
Server Everything tools
No tool names declared yet. Check the project README from the listing page.
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.
PRIMAMCP
{
"mcpServers": {
"primamcp": {
"command": "npx",
"args": [
"-y",
"@planit-tech/primamcp"
]
}
}
}
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
Frequently asked questions
PRIMAMCP is categorized under Legal and uses a local stdio subprocess. Server Everything belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick PRIMAMCP for legal work and Server Everything for other tools and integrations.
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.
PRIMAMCP has no declared pricing — check the project's own site. Server Everything is listed as free. Auth: no auth required. 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 primamcp and modelcontextprotocol-server-everything as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, PRIMAMCP has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 11 GitHub stars. Server Everything has 55/100 (Good) with 9 views, 0 installs and 91,486 GitHub stars.