Dealroom

What Dealroom MCP server does

Dealroom MCP server coordinates asynchronous negotiation between two parties. A deal begins when an initiator selects a contract skill and jurisdiction, then invites a respondent. Both participants provide preferences and firmness levels for individual clauses. After negotiation, the parties can accept the resulting terms and generate a contract for signing.

The platform includes built-in skills for contract types such as NDAs, DPAs, and MSAs. It supports English and Castilian Spanish, with the contract language selected when the deal is created. Additional premium skills can be installed on a self-hosted instance through the project’s licensing system.

For the ⚖️ Legal category, the main distinction is that Dealroom models negotiation as structured clause data instead of treating it only as free-form text exchange. Users can also propose changes to open, negotiable parameters during the negotiation process.

How it works

Dealroom MCP server uses a weighted compromise algorithm to evaluate each party’s position on a clause. Participants provide a firmness value from 1 to 5. Internally, the application converts that value to flexibility and combines it with option bias to calculate each party’s stake. The higher stake determines the clause outcome; equal stakes produce a balanced compromise. A later fairness pass can rebalance results if one party wins too many clauses.

The documented deal lifecycle is:

1. Create a deal and choose a skill, jurisdiction, and language.
2. Invite the other party.
3. Collect clause preferences and firmness values.
4. Suggest or review compromises.
5. Agree on final terms.
6. Generate the contract for signing.

The repository documents an Agent Negotiation REST API for programmatic access. The web application itself is built with Next.js and TypeScript, uses tRPC for its internal API, PostgreSQL with Prisma for persistence, and NextAuth for authentication.

Setup and configuration

Local operation requires Node.js 20 or later, PostgreSQL, and a Resend account for magic-link email. The standard setup installs dependencies, copies .env.example to .env, generates the Prisma client, pushes the database schema, seeds initial data, and starts the development server.

Required configuration includes DATABASE_URL, NEXTAUTH_SECRET, NEXTAUTH_URL, RESEND_API_KEY, and EMAIL_FROM. Google sign-in can be configured with GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET. SKILLS_DIR is available for premium skills, while STRIPE_SECRET_KEY is optional for in-app billing.

A Docker-based sovereign kit packages the application, PostgreSQL, and a migrator for self-hosting. It publishes port 8486 and exposes /api/health for health checks. Optional Caddy support is available for TLS. The project’s deployment documentation covers backups, restoration, scheduled tasks, and hardening.

Tools and capabilities

Dealroom MCP server supports or documents these capabilities:

• Create and invite participants to contract deals.
• Negotiate individual clauses using preferences and firmness levels.
• Calculate weighted compromise suggestions.
• Generate contracts after agreement.
• Run contracts in English or Castilian Spanish.
• Manage skills, customers, and supervisors through administrative portals.

Platform administrators manage the skill catalog, customers, and supervisors. Supervisors can monitor only the deals assigned to them, while ordinary users access their own negotiations.

Limitations and notes

The supplied material documents the agent interface as a REST API, but does not provide MCP transport details, named MCP tool schemas, or client-specific setup instructions. It also does not identify supported MCP clients. Hosted operation is paid per contract when the contract is first downloaded or signing begins; the self-hosted kit has no stated usage caps, while premium skills require separate licensing.

The project is licensed under GNU Affero General Public License v3.0. Deployments that modify Dealroom and provide it as a network service must offer the corresponding source under AGPL section 13.