# From open beta to global GA: What Docusign learned by bringing contract AI workflows to agents

DevFeed: [From open beta to global GA: What Docusign learned by bringing contract AI workflows to agents](<https://devfeed.tech/articles/from-open-beta-to-global-ga-what-docusign-learned-by-bringing-contract-ai-workflows-to-agents-119282.md>)

Original publisher: [Read original article](<https://thenewstack.io/docusign-mcp-server-agents/>)

Author: Carly Page

Published: 2026-11-05T14:50:21Z

Content type: news

Language: en

Sources: [The New Stack](<https://devfeed.tech/sources/the-new-stack.md>)

Topics: [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [experience report](<https://devfeed.tech/topics/experience-report.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [administration](<https://devfeed.tech/tags/administration.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentforce](<https://devfeed.tech/tags/agentforce.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-application](<https://devfeed.tech/tags/ai-application.md>), [ai-workflows](<https://devfeed.tech/tags/ai-workflows.md>), [beta](<https://devfeed.tech/tags/beta.md>), [contract-ai](<https://devfeed.tech/tags/contract-ai.md>), [docusign](<https://devfeed.tech/tags/docusign.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-software](<https://devfeed.tech/tags/enterprise-software.md>), [global](<https://devfeed.tech/tags/global.md>), [information](<https://devfeed.tech/tags/information.md>), [model-context-protocol-mcp](<https://devfeed.tech/tags/model-context-protocol-mcp.md>), [open](<https://devfeed.tech/tags/open.md>), [post](<https://devfeed.tech/tags/post.md>), [security](<https://devfeed.tech/tags/security.md>), [sponsor-docusign](<https://devfeed.tech/tags/sponsor-docusign.md>), [sponsored](<https://devfeed.tech/tags/sponsored.md>), [sponsored-post](<https://devfeed.tech/tags/sponsored-post.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

## AI overview

Docusign's path from MCP open beta in May 2026 to global general availability on September 30 showed that connecting agents to contract tools is easier than making workflows reliable, permission-bound, and clear when requests are ambiguous. Customer feedback expanded agreement workflows, local document uploads in supported MCP Apps clients, and account-level controls. Docusign uses OAuth 2.0 scopes and existing user permissions for tool calls, with account administrators able to enable or disable MCP access; these controls do not determine how third-party AI providers handle received data. A shared server supports multiple AI clients, though client behavior and feature availability can differ. Guided clarification can help agents resolve missing choices before acting. Docusign says MCP complements rather than replaces APIs: APIs suit deterministic processes with defined inputs and outputs, while agents can use MCP to choose tools for broader requests, and both can be combined. Human review and approval remain part of transactions.

## Source excerpt

Connecting an AI agent to enterprise software is relatively easy. Making sure it can find the right information, carry out The post From open beta to global GA: What Docusign learned by bringing contract AI workflows to agents appeared first on The New Stack.