Server Everything vs Zopaf

A side-by-side look at the Server Everything and Zopaf MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Server Everything logoServer EverythingOther Tools and Integrations · Local subprocess (stdio)MCP server that exercises all the features of the MCP protocol55GoodAuth: no auth requiredZopaf logoZopafAgreements & CoordinationNegotiation math engine. Pareto frontier, counteroffer generation, zero LLM tokens.40FairAuth: not declared

Verdict: choose Server Everything for other tools and integrations work as a local process; choose Zopaf for agreements & coordination. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Server Everything logoChoose 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.
Explore Server Everything

Zopaf logoChoose Zopaf when

  • You need dedicated capabilities in the Agreements & Coordination domain.
  • You want tools like create_session, add_issue, set_issue_range.
Explore Zopaf

Feature & specification comparison

Rows where the two servers differ are marked.

SpecServer Everything logoServer EverythingZopaf logoZopaf
CategoryOther Tools and IntegrationsAgreements & Coordination
Quality signal55/100 · Good40/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars91,4860
Directory activity 9 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed9

Tools & capabilities

Server Everything tools

No tool names declared yet. Check the project README from the listing page.

Zopaf tools 9

  • create_sessionCreate a new negotiation session. Returns a session_id used by all other tools.
  • add_issueAdd a negotiable issue/term with options ordered worst to best for the user.
  • set_issue_rangeSet the acceptable range for a numeric issue, enabling 0-100 scoring.
  • record_preferenceRecord that the user prioritizes some issues over others. Updates the weight model.
  • set_batnaRecord the user's alternatives if the deal falls through. Determines leverage.
  • generate_counteroffersGenerate 3 iso-utility counteroffers to present simultaneously.
  • process_counterpart_responseProcess the counterpart's reaction to infer their priorities and generate a round-2 offer.
  • analyze_dealScore a specific deal against the Pareto frontier. Shows value captured and suggested trades.
  • get_negotiation_stateGet current model state: issues, weights, BATNA, frontier size, and recommended next step.

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 (Claude Desktop / Cursor)
{
  "mcpServers": {
    "modelcontextprotocol-server-everything": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-everything"
      ]
    }
  }
}

Zopaf

No confirmed install command for Zopaf yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Server Everything is categorized under Other Tools and Integrations and uses a local stdio subprocess. Zopaf belongs to Agreements & Coordination and uses an install path we have not confirmed yet. Pick Server Everything for other tools and integrations work and Zopaf for agreements & coordination.

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. Zopaf has no confirmed install command yet — follow its own setup instructions.

Server Everything is listed as free. Auth: no auth required. Zopaf 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 zopaf 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 55/100 (Good) with 9 views, 0 installs and 91,486 GitHub stars. Zopaf has 40/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.