Can AI agents automate Docusign eSignature?

Docusign eSignature is automatable today through a mature REST API. This record is eSignature only, not Oneflow, Adobe Acrobat Sign, or Dropbox Sign. The eSignature REST API uses a data-center base path plus /restapi. Demo calls go to https://demo.docusign.net/restapi; production base URIs come from OAuth userInfo. Every call needs a Bearer access token. Docusign documents Authorization Code Grant (confidential apps use a client secret) and JWT Grant (requestJWTUserToken for a specific user). Official SDKs wrap the API in C#, Java, Node.js, PHP, Python, and Ruby. Docusign Connect sends envelope and recipient events to a listener; the Power Automate connector says an administrator must enable Connect. Docusign documents a first-party MCP server in Open Beta at developers.docusign.com/platform/mcp-server/. It accepts only Confidential Authorization Code Grant tokens, is described as limited-availability, and requires a human in the loop. The MCP Registry listing co.thisdot.docusign-navigator/mcp is a third-party Navigator server and is not treated as first-party eSignature MCP. Zapier, Make, and Microsoft Power Automate publish Docusign envelope connectors. A built-in n8n node was not established. No eSignature CLI was established; the IAM Toolkit ds commands target Agreement Manager, which is outside this product boundary. Computer-use viability is unassessed. API scores 8 and is the best path. MCP stays at 6 because it is a vendor beta with an OAuth-type gate.

Best path today: api · Overall automatability: 8/10