Docusign MCP Server Goes GA: What to Build Before Sept 30

Docusign announced that its MCP Server reaches general availability on September 30, making the e-signature platform's capabilities callable by any AI agent that speaks the Model Context Protocol without custom adapter code. The server, live in beta now at mcp.docusign.com/mcp in production and mcp-d.docusign.com/mcp in dev, exposes four capabilities — sending envelopes, checking signing status, querying Navigator, and triggering Maestro workflows — and is backed by Docusign Iris, the company's purpose-built AI for contracts. Docusign processes over a million documents daily across $2 trillion in agreement workflows, and the GA follows the MCP 2026-07-28 specification that added a stateless core, W3C Trace Context, and OAuth 2.0/OpenID Connect hardening; Salesforce shipped MCP GA in April 2026, and HubSpot, Zendesk, Notion, and Workday are expected in Q3 2026.

September 30 is the date AI agents officially get to sign contracts. Docusign announced this month that its MCP Server reaches general availability on that day — which means any agent that speaks MCP can reach into the world’s dominant e-signature platform without a single line of custom adapter code. This isn’t a startup experiment. Docusign processes over a million documents daily across $2 trillion in agreement workflows. That infrastructure is now agent-accessible. What the Server Exposes The official Docusign MCP server sits at https://mcp.docusign.com/mcp production and https://mcp-d.docusign.com/mcp dev , and it wraps four capabilities your agents can call: - Send envelopes — create signing requests from scratch or from templates - Check signing status — poll whether a document has been viewed, signed, declined, or voided - Query Navigator — natural-language access to AI-extracted agreement data example: “show me pending contracts with XYZ Corp” - Trigger Maestro workflows — launch multi-step approval chains: routing, legal review, obligation tracking Maestro deserves a callout. It is not a webhook — it is a full approval orchestration engine. Triggering it from an agent means the agent can hand off to a governed, human-in-the-loop process and resume when it completes. That is the pattern most enterprise workflows actually need. Connect Before September 30 The server is live in beta now. Here is the fastest path to a working integration: 1. Log into your Docusign developer account https://developers.docusign.com/platform/mcp-server/ and open Apps and Keys 2. Create a new Integration Key — this becomes your Client ID 3. Note the Client Secret 4. Set your agent’s MCP server URL to https://mcp-d.docusign.com/mcp 5. Use the Dev Console accessible directly from your production account to monitor demo and production usage from one dashboard If you are connecting via Claude Desktop, the luthersystems community implementation https://github.com/luthersystems/mcp-server-docusign shows the config pattern: environment variables DS AUTH BASE, DS INTEGRATION KEY, DS USER ID, and DS PRIVATE KEY PATH. For the Navigator query surface specifically, the thisdot Navigator MCP https://github.com/thisdot/docusign-navigator-mcp is worth examining. What Docusign Iris Adds The Docusign MCP server is not a REST wrapper with an MCP label. It is backed by Docusign Iris, the company’s purpose-built AI for contracts. When your agent queries an agreement through Iris, it receives structured, AI-extracted data — not raw document text. Iris understands past negotiations, accepted clauses, company policy, and risk signals. In practice: you can ask “does this contract’s liability cap match our standard?” and receive a direct answer. That is the difference between a tool that accesses agreements and one that understands them. Why the MCP Spec Timing Matters The MCP 2026-07-28 specification https://blog.modelcontextprotocol.io/posts/2026-07-28/ shipped weeks before Docusign’s announcement, and the timing is not coincidental. The new spec brought a stateless core — no bidirectional handshakes, no sticky sessions, no shared session stores. A Docusign MCP server now runs behind a plain round-robin load balancer. The spec also added W3C Trace Context for OpenTelemetry and OAuth 2.0/OpenID Connect authorization hardening that enterprises require. Enterprise-grade MCP deployment was theoretically possible before the July spec. Now it is operationally straightforward. That is the unlock Docusign and every other SaaS vendor was waiting for. The Pattern Is Accelerating Docusign is not the only one. Salesforce shipped MCP GA in April 2026. ServiceNow launched its MCP Server Console. HubSpot, Zendesk, Notion, and Workday are expected in Q3 2026. The MCP server list is beginning to read like an enterprise SaaS directory. For developers, the downstream effect is composability. A Docusign plus Salesforce MCP integration means an agent can pull deal terms from the CRM, generate the contract, route it through Maestro for approval, and send the envelope — without any custom glue code between systems. That end-to-end workflow existed before MCP. Building it used to take weeks of integration work. Building it now takes a day. GA is September 30. The New Stack’s breakdown https://thenewstack.io/docusign-mcp-agentic-agreements/ covers the enterprise architecture in depth, and the official announcement https://www.nasdaq.com/press-release/docusign-agreement-layer-agentic-enterprise-coming-every-agent-2026-09-04 has the full scope. Start with the dev endpoint, connect your agent stack, and test the Navigator query tool first — that is where most of the interesting capability lives before you add write operations.