š Hey #DocusignDevs! At Momentum '26, we shipped tools designed to help you build agentic agreement workflows.
Here's what's live:
- Agent Studio (Early Access): Build & govern custom agents inside IAM using natural language
- MCP Server (Global Open Beta): Expose Docusign tools to Claude, Gemini, and other MCP clients
- Agreement Manager API (GA): Bulk ingest agreements and trigger downstream workflows
- IAM Toolkit (Open Beta): CLI-based, config-as-code deployment across accounts
- Developer Console (Open Beta): Manage keys, promotion, and monitoring in one place
Read the full launch blog. docusign.com/blog/developersā¦
Agreement tasks slow sellers down. With the Docusign MCP connector in Microsoft Copilot Studio, you can build an agent that handles it:
- Check if there's an active NDA with a customer
- Send agreements using standard templates
- Trigger workflows that fetch CRM data and route for signature
All from Microsoft 365 Copilot or Teams. No custom integration code. Read the full guide to build your agreement agent. docusign.com/blog/developersā¦
What makes enterprise AI automation actually work? The right abstractions.
The Docusign MCP Server gives AI agents a clean interface into agreement intelligence, and this Microsoft Foundry build puts it to work on one of enterprise's most manual headaches: contract price adjustments.
From contract discovery to inflation calculation to signature routing, it's fully automated. Pro-code or low-code, teams can start where they are and scale as needed, without re-architecting. This is what the agentic enterprise looks like.
š Read the full build. techcommunity.microsoft.com/ā¦
Building agentic agreement workflows on @OpenAI Codex? The Docusign connector is now available in your toolkit. š ļø Powered by our MCP Server, get secure, structured access to agreement intelligence right where youāre already building.
Learn more. prnewswire.com/news-releasesā¦
š¤ Big news for business teams š Docusign IAM is now available in @openai Codex and ChatGPT ā create agreements, review contracts, manage renewals, and take action right where work happens. Less searching. Less busywork. More action. š
Most financial onboarding workflows break at the handoffs, identity verified in one system, bank account checked in another, agreement generated somewhere else. Data gets re-entered. Errors surface late. NIGO issues slip through.
This sample architecture closes those gaps. Using Docusign IAM J.P. Morgan Payments Validation Services, the flow runs in one unified runtime:
- Applicant fills one form
- Entity Validation confirms identity (KYC)
- Account Validation confirms routing ownership
- Both pass ā agreement generated and sent for eSignature
The same pattern applies to loan applications, vendor onboarding, and compliance recertification.
Check out the full architecture GitHub reference implementation. docusign.com/blog/developersā¦
What an exciting time to be building, #DocusignDevs! š
Last week we wrapped #Momentum26 alongside an incredible community of customers and partners exploring whatās next for agentic agreement workflows.
From technical builder sessions to conversations at our booth around real-world implementation patterns and agentic experiences, the energy was exciting to see first hand.
Huge thank you to everyone who stopped by, built with us, shared feedback and ideas, and joined in on the agentic raffle fun!
Looking forward to the next one. In the meantime, check out our recent blog to see what shipped. š„³
Docusign unveils MCP Server, Agreement Manager API, IAM Toolkit, and Developer Console at Momentum 2026 to bring agentic AI to enterprise agreements.
Thanks to Docusign thenewstack.io/docusign-mcp-ā¦
POV: the raffle is the demo š
Enter by chatting with Claude. Sign your entry with Docusign. Win a Nintendo Switch 2, Bose Headphones, or a Lomo Instant camera ā all at the builder booth at #Momentum26 š¤š„³
Legacy agreement stacks werenāt built for AI-ready workflows.
The Docusign Agreement Manager API (GA) helps teams ingest millions of agreements with predictable performance, enterprise-grade security, and low integration friction.
Centralize agreements, then extract the data your agents and downstream systems need. š¤
š Learn more. docusign.com/blog/programmatā¦
Good morning, NYC āļø
The energy from last night is still in the room. Day 2 of #Momentum26 is here.
Keynote ā builder sessions ā product roadmap ā braindates ā expo lounge. Full day. Letās go. š
Hey #DocusignDevs, turning post-signature agreement data into scalable, automated action is still one of the harder problems in the stack. Let's fix that.
At #Momentum26, we'll be walking through how to centralize agreement data, apply AI-powered extractions, and trigger event-driven workflows, unlocking real-time insights and AI-ready architectures.
- Leverage structured agreement data post-signature with Navigator API for downstream systems and analytics
- Trigger real-time workflows with APIs and events throughout the agreement lifecycle
- Customize AI extractions for your unique business needs
š Thursday, May 21 at 1:15 PM ā 1:45 PM ET
š Javits Center, NYC
Register free and add this session to your agenda. momentum.docusign.com/momentā¦
*Adds session to #Momentum26 agenda ā*
If you're building AI agents, agreement data shouldn't be a black box. At Momentum, developers will see how to extend Docusign natively and connect external agents via MCP server for real, production-grade agent experiences.
- Summarize agreements and trigger cross-system actions with agentic workflows
- Enable secure, natural-language interactions with agreement data via MCP ā - Build on a platform evolving specifically for trustworthy agents at scale
š Thursday, May 21 at 2:00 PM ā 2:30 PM ET
š Javits Center, NYC
Register free. momentum.docusign.com/momentā¦
Agreement management is moving into the systems where work happens: CRMs, procurement platforms, and custom apps.
At #Momentum26, we're showing you how to make it work in practice and scale with speed and control.
- Integrate end-to-end systems to eliminate duplicate data entry and copy-paste errors
- Modernize with Data Verification using out-of-the-box and custom extension apps
- Embed agreement workflows directly into your apps to automate broader business processes
Add this session to your agenda for a live technical demo and architecture patterns you can walk away with.
š Thursday, May 21 at 12:30 PM ā 1:00 PM ET
š Javits Center, NYC
Register free. momentum.docusign.com/momentā¦
For most enterprises, managing contract price adjustments across thousands of agreements means expiration tracking, BLS CPI lookups, price recalculations, approval chains. The process works until it doesn't, and at scale it rarely does.
š Anahita Afshari, Cloud Solution Architect at Microsoft replaced that with a four-agent system built on Microsoft Foundry, using the Docusign MCP server to connect the full Docusign Intelligent Agreement Management (IAM) platform into one automated pipeline.
Docusign Navigator and Maestro handle agreement intelligence and workflow orchestration. Microsoft Foundry provides the AI reasoning layer. MCP is the protocol that makes them composable: one standard that lets Foundry agents access the full Docusign ecosystem, with every new capability automatically available as a new tool.
š ļø See how it's built. techcommunity.microsoft.com/ā¦
Excited to share this new success story from @Docusign highlighting how we scaled partner integrations using Docusign Maestro and their Extension App framework.
By integrating once with Docusign, our customers can securely route signed agreementsāfrom closing docs to wills and insurance policiesādirectly into a subscriberās secure vault without custom integrations for every partner.
Proud of this collaboration and excited for whatās ahead!
Every new partner used to mean a new engineering project. š ļø
@prisidio_inc replaced per-partner custom builds with a single Docusign workflow. Their extension app owns one step, everything else is handled upstream.
Zero custom engineering on either side.
The pattern: find the workflow step your partners already share. Build around that layer. Stop rebuilding from scratch.
Full story with Prisidio CTO Andrew Dean. docusign.com/blog/developersā¦
Having previously built and sold a startup to @Docusign, itās especially rewarding to see what weāre now building together at @prisidio_inc.
Excited to share this new success story highlighting how weāre using Docusign Maestro and the Extension App framework to securely route important signed agreements directly into a subscriberās vault ā without custom integrations for every partner.
Proud of this collaboration and excited for whatās ahead.
Every new partner used to mean a new engineering project. š ļø
@prisidio_inc replaced per-partner custom builds with a single Docusign workflow. Their extension app owns one step, everything else is handled upstream.
Zero custom engineering on either side.
The pattern: find the workflow step your partners already share. Build around that layer. Stop rebuilding from scratch.
Full story with Prisidio CTO Andrew Dean. docusign.com/blog/developersā¦
Every new partner used to mean a new engineering project. š ļø
@prisidio_inc replaced per-partner custom builds with a single Docusign workflow. Their extension app owns one step, everything else is handled upstream.
Zero custom engineering on either side.
The pattern: find the workflow step your partners already share. Build around that layer. Stop rebuilding from scratch.
Full story with Prisidio CTO Andrew Dean. docusign.com/blog/developersā¦
Connecting specialized legal AI usually means high-friction, one-off builds. Weāre changing that. š ļø
The Docusign MCP Server standardizes how AI systems connect to agreement workflows.
Dive into 2 implementation patterns. docusign.com/blog/developersā¦
OAuth is the security foundation of every Docusign Extension App, but the role it puts you in isn't what you'd expect.
Docusign acts as the client calling your APIs. Your app acts as both the authorization server and the resource server, meaning you build the endpoints, issue the tokens, and validate every incoming request.
No token ā no access.
Invalid token ā request rejected.
Expired token ā re-authentication required.
Full breakdown of both OAuth flows, required endpoints, token lifecycle, and common pitfalls. docusign.com/blog/developersā¦