API Governance vs Zopaf
A side-by-side look at the API Governance and Zopaf MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose API Governance for agreements & coordination 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?
Choose API Governance when
- You need dedicated capabilities in the Agreements & Coordination domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CODERIFTS_API_KEY. - You want tools like
preflight_change_set, verify_receipt, get_decision_details.
Choose Zopaf when
- You need dedicated capabilities in the Agreements & Coordination domain.
- You want tools like
create_session, add_issue, set_issue_range.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Agreements & Coordination | Agreements & Coordination |
| Quality signal | 55/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CODERIFTS_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 3 | 9 |
| Full listing | View API Governance | View Zopaf |
Tools & capabilities
API Governance tools 3
preflight_change_setPreflight a complete base→head change set of contract artifacts. Returns risk score and breaking-change analysis. With `preflight_mode: "authorize"` (and `context.operation`), returns a governance decision (ALLOW / WARN / REQUIRE_APPROVAL / BLOCK) and may mint a signed chain-receipt. With `prefligh…verify_receiptVerify a signed chain-receipt you already hold: signature authenticity, body binding, and (when lifecycle indices are available) whether it is currently authorized for a stated operation/target. Requires `token`. Does not re-diff specs.get_decision_detailsRetrieve a past decision by `decision_id` (preferred) or `fingerprint`: stored report, breaking changes, scores, and linked receipt metadata if present. Not for a new analysis of the current change set.
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.
API Governance
{
"mcpServers": {
"api-governance-2": {
"command": "npx",
"args": [
"-y",
"coderifts"
],
"env": {
"CODERIFTS_API_KEY": "YOUR_CODERIFTS_API_KEY_HERE"
}
}
}
}
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
API Governance is categorized under Agreements & Coordination and uses a local stdio subprocess. Zopaf belongs to Agreements & Coordination and uses an install path we have not confirmed yet. Pick API Governance for agreements & coordination 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.
API Governance has no declared pricing — check the project's own site. 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 api-governance-2 and zopaf as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, API Governance has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Zopaf has 40/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.