In-depth architectural comparison of the Service agreement and Bill of sale MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Service agreement
Legal · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Bill of sale
Legal · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Service agreement if you need specialized Legal tools running via a local process. Choose Bill of sale if your workspace requires Legal integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
S
Choose Service agreement when:
You need dedicated capabilities in the Legal domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Write an agreement: parties, scope, deliverables, rate and payment terms, dates, termination notice, liability cap, jurisdiction. Stores it and returns the rendered Markdown. Returns `SA-YYYY-NNNN
agreement_get
Read one agreement in full by SA number or client name, with its status history
agreement_list
List agreements newest first; filter by status and client
agreement_update_status
Move the agreement exactly one step -- draft, sent, signed, expired -- stamping date and note into its history
clause_library
The five built-in clauses: IP assignment, mutual confidentiality, late payment interest, kill fee, revision rounds. Pro: full texts with the agreement's variables filled in
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Service agreement is categorized under Legal and uses a local stdio subprocess. In contrast, Bill of sale belongs to Legal using local stdio subprocess. Select Service agreement when you need capabilities focused on legal and Bill of sale when you require tools for legal.
Render for signing: Markdown, or self-contained HTML with print CSS (Pro). Includes the signature block and the template-not-legal-advice line
agreement_checklist
The before-you-send-it checklist: missing fields and one-sided gaps flagged neutrally
license_status
Free or Pro, and the key
Bill of sale Tools (9)
sale_create
Record a sale and generate the bill of sale: seller, buyer, item with VIN/serial/IMEI where it has one, price in minor units, date. Returns `BOS-YYYY-NNNN`. An identical repeat sale is refused unless you confirm it
sale_update
Change anything on a draft before signing: price, parties, item details, identifiers, the as-is clause, warranty, notes. Empty string clears an optional field
sale_finalize
Freeze the draft into the signing copy. From here `sale_update` refuses it and every render prints without the DRAFT watermark
sale_list
Every bill of sale, newest first: id, status, date, item, buyer, seller, price. Filter to drafts or finalized
sale_get
One bill of sale in full by its BOS number
sale_delete
Delete a draft outright; a finalized document needs `confirm_finalized: true`. The number is never reissued, so a gap in the series is the record of the deletion
sale_render
Print the document: Markdown, a self-contained HTML file for print-to-PDF, or both, with signature lines. Drafts carry a DRAFT watermark so a review copy cannot be signed by mistake
sale_summary
The book at a glance: draft and finalized counts, total value per currency. Currencies are never added together