Contractbook

@contractbook list all templates we have for employment agreements and show me the required fields for each one

Found 3 employment agreement templates in your Contractbook workspace: 1. **Standard Employment Contract** (ID: tmpl_abc123) — requires: employee_name, start_date, salary, job_title, department 2. **Contractor Agreement** (ID: tmpl_def456) — requires: contractor_name, project_scope, rate, payment_terms 3. **NDA + Employment Hybrid** (ID: tmpl_ghi789) — requires: employee_name, confidentiality_period, start_date, compensation Each template includes pre-configured signing parties and can be used with the create-document tool to generate a draft.

This example shows template discovery before document creation. The MCP returns template IDs and field schemas but does not expose the full document text or clauses — you'll need Contractbook UI access to review legal language. Useful for understanding what data you need before drafting.

@contractbook create a new employment contract from template tmpl_abc123 for Sarah Chen, starting March 1st 2025, salary $95000, title Senior Designer

Created draft document **Employment Contract - Sarah Chen** (ID: doc_xyz789) from your Standard Employment Contract template. Populated fields: - Employee Name: Sarah Chen - Start Date: March 1, 2025 - Annual Salary: $95,000 - Job Title: Senior Designer The draft is saved in Contractbook but not yet sent for signature. You can review it in the Contractbook UI, make manual edits, or use the send-for-signature workflow when ready.

This write action creates a draft only — it does not trigger signature requests or notify parties. You must separately initiate signing through Contractbook's UI or a send tool if available. The MCP requires exact template field names; mismatched fields will cause creation to fail, so always fetch the template schema first.

@contractbook find all unsigned documents from the last 30 days and summarize which ones are blocking new hires

Found 7 unsigned documents created in the last 30 days. Of these, 4 are employment-related and likely blocking onboarding: - **Employment Contract - Sarah Chen** (created Feb 15) — awaiting candidate signature - **Offer Letter - Marcus Liu** (created Feb 10) — awaiting HR countersignature after candidate signed - **Contractor Agreement - Priya Sharma** (created Feb 8) — awaiting legal review, not yet sent - **NDA - Alex Kim** (created Feb 5) — awaiting candidate signature The other 3 documents are vendor agreements unrelated to hiring. Recommend prioritizing Marcus Liu's contract since the candidate has already signed their portion.

This synthesis example pairs the MCP's list-documents filter with AI reasoning to surface blockers. The MCP returns document metadata (status, dates, parties) but not the full contract text, so the AI infers hiring relevance from titles and signing state. Accuracy depends on consistent document naming conventions in your Contractbook workspace.

When Contractbook beats spreadsheet-and-DocuSign for vendor intake

A 10-person startup onboards 3-5 new vendors a month—SaaS tools, freelance designers, occasional consultants. The ops lead used to copy-paste an NDA template in Google Docs, export to PDF, then chase signatures in DocuSign. Contractbook wins here because the MCP lets you script the entire flow: list templates, create draft from the NDA template with the vendor's name and scope pre-filled, get the PDF link, then hand off to the vendor in Slack. The 9 tools cover discovery (list templates, list documents), drafting (create from template, get document), and export (get PDF link). The threshold: if you're signing fewer than 2 contracts a month, the API-key setup overhead isn't worth it—just stay in DocuSign's UI. But once you hit recurring vendor intake, the MCP turns a 6-step manual process into a one-prompt handoff.

Contractbook for read-only contract search, not live negotiation

A 15-person fintech runs monthly compliance checks: the CFO needs to pull every vendor contract signed in the last quarter, verify insurance clauses, and export PDFs for the auditor. The MCP's list-documents tool filters by date and status, get-document pulls the full text, and get-PDF-link hands the auditor a download URL. This is a pure read workflow—no drafting, no sending for signature. Contractbook's MCP shines here because the alternative is clicking through the web UI and downloading PDFs one by one. The limitation: the MCP doesn't parse contract clauses or flag missing terms; you still need a human to read the insurance section. If your audit process is 'find all contracts and export', this MCP saves 90 minutes a month. If you need semantic search across clauses, you're better off with a legal-AI tool that ingests the PDFs.

When template-driven SOWs justify the Contractbook integration

A 4-person creative agency closes 8-12 client projects a year, each starting with a statement-of-work that varies only in scope, timeline, and fee. The founder used to duplicate a Google Doc, hand-edit the variables, then email a PDF. Contractbook's create-from-template tool lets the team generate the SOW draft in Switchy by passing client name, deliverables, and payment terms as overrides—no manual copy-paste. The get-template tool shows which fields are available before you create the draft, so you're not guessing at field names. The trade-off: this MCP doesn't send the draft for signature; you still open Contractbook's UI to trigger the signing flow. If your agency closes fewer than 6 deals a year, the setup tax isn't worth it. But once SOW generation becomes a monthly task, scripting the draft step cuts 15 minutes per contract and eliminates the 'forgot to update the client name' error.