Proposal Drafting with MCP: A Step-by-Step Playbook

Proposal drafting is the job of turning a sales conversation into a document a client can sign. Account managers and agency owners often rebuild each one from an old file, copying scope, pricing and terms by hand. With MCP, an AI assistant can find your best past proposals, pull deal details from the CRM, fill a copy of your template and prepare it for e-signature.

This playbook uses document storage (Google Drive or Box), your CRM and Docusign. Pricing, legal terms and the final send stay with a person.

What you need

• Document storage. Either Google's Workspace MCP servers (Drive and Docs) or Box's hosted server. See the Google Workspace MCP server profile and the Box MCP server profile. Google's servers are in Developer Preview as of October 2026.
• CRM context. For HubSpot, search_crm_objects and get_crm_objects pull the deal and contact. See the HubSpot MCP server profile.
• E-signature. The Docusign MCP server, at https://mcp.docusign.com/mcp for production and https://mcp-d.docusign.com/mcp for its demo environment.
• Approved source material. A proposal template, a current price list and a library of past proposals you are happy to reuse.
• An AI client supported by each server. Docusign's developer guide lists setup guides for Claude, ChatGPT, Microsoft Copilot Studio, Perplexity and others.

The workflow

1. Gather the deal facts. Use HubSpot's search_crm_objects to find the deal and get_crm_objects for the contact and company. Ask for scope notes, budget, decision date and stakeholders.
2. Find similar past proposals. In Google Drive, search_files and list_recent_files find candidates and read_file_content reads them. In Box, use search_files_keyword or search_files_metadata, then get_file_content.
3. Ask questions across documents. Box's ai_qa_multi_file asks Box AI a question across several files, for example "how have we scoped SEO retainers for clinics?" Box's tools page lists it as on by default.
4. Copy the template. In Drive, copy_file makes a fresh copy of your proposal template. In Box, copy_file does the same, or Doc Gen tools (list_docgen_templates, get_docgen_template_by_id) work with Doc Gen templates if you use them.
5. Fill the draft. In Google Docs, update_doc edits the copied document. Ask the assistant to fill scope, timeline and deliverables, and to leave pricing as clearly marked placeholders.
6. Insert pricing by hand or from an approved sheet. If your price list lives in Google Sheets, get_values reads it. A person checks every number before it goes to the client.
7. Review. The account owner reads the full draft. Legal or a partner reviews any changed terms.
8. Prepare for signature. With Docusign, getTemplates lists your templates and createEnvelope creates an envelope with documents, recipients and tabs. resolveEnvelopeSendMethod returns step-by-step instructions for sending, per Docusign's guide.
9. Track and nudge. getEnvelope returns status and listRecipients shows who has signed. sendReminder notifies pending recipients. Docusign's updateEnvelope can void envelopes and send drafts, so keep it on approval.

Example prompts

• "Find the HubSpot deal for Acme Dental and summarize scope notes, budget, decision date and contacts. Read only."
• "Search Drive for proposals from the last 12 months with 'SEO retainer' in the title. List the five closest matches to this deal and why."
• "Copy our 'Proposal template 2026' with copy_file, name it 'Acme Dental proposal draft', and fill the scope and timeline sections from the deal notes. Leave every price as [PRICE TO CONFIRM]."
• "Compare this draft with our last two signed retainer proposals. List any term or deliverable that differs."
• "List my Docusign templates. Do not create an envelope yet."

Guardrails

• Never edit the master template. Work on copies only. Google's Workspace MCP setup guide lists drive.readonly and drive.file as the Drive scopes; grant read-only first and add more only when a step needs it.
• Box admins control risky tools. Box marks add_file_shared_link as off by default, noting it can create open links or add outside collaborators. Leave it off. Box also says MCP "does not bypass Box permissions."
• Test signing in demo first. Docusign recommends custom connectors only with a developer (demo) account and the official connector for production. It warns that a custom connector pointed at production "could unexpectedly consume your production API quota during testing."
• Sending is a legal act. An envelope goes to real signers. Keep approval prompts on for createEnvelope, updateEnvelope and updateEnvelopeRecipients, and have the owner confirm recipients.
• Watch for injected text. Client documents and emails can carry instructions aimed at the AI. Read MCP prompt injection and the MCP Security Center.
• Keep pricing and terms human. The AI drafts the narrative. People set prices, discounts and liability terms.

What to measure

• Time from "proposal requested" to "proposal sent," before and after.
• Revision rounds per proposal, internal and with the client.
• Errors caught in review: wrong client name, wrong scope, stale pricing.
• Time from envelope sent to completed, from getEnvelope status.
• Win rate by proposal type, tracked over a long enough period to mean something.

Next step

Clean up your template and pick three past proposals you would happily reuse. Then run the workflow on one live deal with full review. Other task guides are in the MCP playbooks hub. If you want a proposal workflow built around your own documents and approvals, talk to us about MCP development.

Frequently asked questions