Docusign MCP server GA: agents can now send your contracts
The Docusign MCP server is generally available on September 30. Claude, ChatGPT and Copilot can send and track agreements. Set the approval step first.
The Docusign MCP server is generally available as of September 30. Claude, ChatGPT, Gemini, Copilot, Slack and any other Model Context Protocol client can now reach Docusign directly. An agent can send an envelope, check its status, start a workflow and read clause data from your signed agreements. That is useful. It also means a prompt can now put a contract in front of a customer. Decide who approves that before you connect it.
What actually happened
Per Docusign's announcement, the MCP server exposes Docusign's agreement tools and its Iris AI engine to any MCP client. Agents can analyze agreement terms, run workflows, send contracts and track documents. Docusign lists account-level admin controls, multi-region infrastructure and multilingual support. Salesforce, Slalom and Experian were among the beta users.
The Claude connector guide gives the practical detail. You connect with OAuth: you sign in to Docusign and grant access. The tools cover envelope sending and status, Workflow Builder triggers, and Agreement Manager queries for clauses, key dates and metadata. Actions run inside your existing Docusign permissions and audit policies.
Docusign also says two things directly. Results vary by AI model, and sensitive workflows may need human review or approval steps. We agree with both.
Why the Docusign MCP server matters for your business
For a small business, the good use is obvious. "Send the standard service agreement to the client from yesterday's call" is now a single request. "Which vendor contracts auto-renew in the next 60 days?" is a real query against real clause data, not a spreadsheet you forgot to update.
The risk is just as clear. We would set it up like this:
Read first, send later. Start with status checks and clause lookups. Add sending after a few weeks of clean results.
Templates only. Let the agent send only approved templates with filled fields. Do not let it draft free-form contract language.
Scope the OAuth user. Connect with a Docusign user whose role can send only what you would let a new hire send. The agent inherits that role, so that role is your guardrail.
Keep a human on the send button for money. Anything with pricing, payment terms or liability gets a person's review before it leaves.
Key takeaways
- The Docusign MCP server became generally available on September 30
- Claude, ChatGPT, Gemini, Copilot, Slack and any MCP client can connect through OAuth
- Agents can send envelopes, track status, trigger Workflow Builder and query clause data through Iris
- Actions run inside your existing Docusign permissions and audit policies
- Start read-only, restrict sends to templates, and keep human approval on anything with money in it
An agent that can send a contract needs an approval step you control. We wire AI assistants into tools like Docusign with scoped accounts, template-only actions and a human checkpoint where it counts. See how we build approval-gated automation, or tell us which paperwork eats your week.
Sources: Docusign newsroom, Docusign developer blog.
- #docusign
- #mcp
- #ai-agents
- #contracts
- #approval-workflows
Tommy Rush — Founder, Rush Commerce
Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More
Get The Rush Report weekly — one email, zero fluff.
Keep reading
White House AI accord is morally binding. Audit your vendors
Six AI leaders signed a White House AI accord on internal controls and outside auditors. It has no legal teeth. What your vendor contracts should say instead.
Read itOpenClaw Enterprise: a free agent control plane, pilot only
OpenClaw Enterprise is an MIT-licensed, self-hosted control plane for persistent AI agents from OpenAI, Red Hat and Nvidia. It is free, and it is pre-1.0.
Read it