Dealroom vs Contracts
A side-by-side look at the Dealroom and Contracts MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
D
DealroomLegalMake a contract in one call, or negotiate it clause by clause with a published compromise formula.33EmergingAuth: not declaredC
ContractsLegal · Remote HTTP/SSEContract drafting, statute-cited US state law requirements, non-compete checks, risk analysis.42FairAuth: not declaredVerdict: choose Dealroom for legal work; choose Contracts for legal over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
DChoose Dealroom when
- You need dedicated capabilities in the Legal domain.
- You have the keys it needs:
DATABASE_URL, NEXTAUTH_SECRET, NEXTAUTH_URL, RESEND_API_KEY, EMAIL_FROM.
CChoose Contracts when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | D Dealroom | C Contracts |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 33/100 · Emerging | 42/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | DATABASE_URLNEXTAUTH_SECRETNEXTAUTH_URLRESEND_API_KEYEMAIL_FROM | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Dealroom | View Contracts |
Tools & capabilities
Dealroom tools
No tool names declared yet. Check the project README from the listing page.
Contracts 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.
Dealroom
No confirmed install command for Dealroom yet — follow the setup steps linked from its listing page rather than a guessed package name.
Contracts
{
"mcpServers": {
"contracts": {
"url": "https://www.pactlio.com/mcp"
}
}
}
Frequently asked questions
Dealroom is categorized under Legal and uses an install path we have not confirmed yet. Contracts belongs to Legal and uses a remote HTTP/SSE transport. Pick Dealroom for legal work and Contracts for legal.
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. Dealroom has no confirmed install command yet — follow its own setup instructions.
Dealroom has no declared pricing — check the project's own site. Contracts 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 dealroom and contracts as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Dealroom has a quality signal of 33/100 (Emerging) with 0 views, 0 installs and 1 GitHub stars. Contracts has 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.