What If Sending a Contract Took One Sentence? Build a Docusign AI Agent With MCP in Copilot Studio
Build a Docusign AI agent in Copilot Studio with MCP that sends agreements for signature from a plain request, with no flows or custom connectors to build.
MICROSOFT COPILOT STUDIOAI AGENTSMCP
7/31/20254 min read
From Request to Signed Agreement in One Step
Sending an agreement for signature is a small task that takes more steps than it should: open Docusign, find the right template, fill in the recipient, write the message, send it, then check back later to see where it stands. Multiply that by every offer letter, lease, or NDA a team sends, and it adds up.
This post builds an agent in Microsoft Copilot Studio that does it from a plain request. Ask it to send a document, and it picks your template, fills in the details, and sends the envelope. Ask what templates you have or what account you are on, and it tells you.
What makes it quick to build is MCP, the Model Context Protocol. Instead of wiring up a separate connector or flow for every action, you add one Docusign MCP server and the agent gets all of its actions at once.
Watch the Full Walkthrough First
The video explains MCP, builds the agent from a blank start, sends a real test envelope, and signs it. It also shows what the same work looks like with traditional flows, which makes the difference obvious.
What MCP Is, in Plain Terms
MCP is an open standard, created by Anthropic, for connecting AI to other systems. Its own documentation compares it to a USB-C port: one standard plug instead of a different cable for every device.
There are three parts:
The host: the AI application, in this case Copilot Studio
The client: the piece inside the host that holds the connection
The server: the program that exposes a system's actions, here the Docusign MCP server
Because every MCP server follows the same standard, Copilot Studio can connect to it without custom code. The server describes its own actions, and the agent figures out when to use them. MCP support in Copilot Studio is now generally available, so you no longer need the preview site the video starts from.
What You Need
Access to Microsoft Copilot Studio. The Docusign MCP connector is a premium connector, so check your Copilot Studio licensing
A Docusign account. If you only want to try it, Docusign offers a free developer sandbox account, which is what the video uses
At least one Docusign template. The agent sends from templates, so it has nothing to send until one exists
How to Build the Docusign Agent
Create the agent
In Copilot Studio, select Create, then New agent, and go straight to the full configuration
Name it (the video uses My First MCP Agent) and give it an icon. Description and instructions can wait; this build works without them
Add the Docusign MCP server
Under Tools, select Add a tool and switch to the Model Context Protocol tab. The list of MCP servers keeps growing
Search the Connectors tab for Docusign first if you want to see the alternative: dozens of separate connectors, one per action, such as adding a recipient or listing envelopes. The MCP server replaces all of that with one connection
Select the Docusign MCP server, create a connection, and sign in to your Docusign account. Look for the green check mark, then choose Add and configure
Review what the server can do
The server lists its tools. In the video, there were three: send an envelope from a template with a custom email message, list your templates, and get your account details
Docusign has since announced a broader MCP server, with general availability set for September 30, 2026, adding things like agreement status and insights. Check the tool list in your own connection to see what you have
Under additional details, there is an option to ask the user before running. The video leaves it off for testing. For a real business agent that sends agreements, turning it on adds a confirmation step before anything goes out
Create a template in Docusign
In Docusign, open Templates and create one: give it a name, add a document, set the email subject and message, add a recipient, and place the signature fields
The agent's first test in the video failed for exactly this reason. It replied that there were no templates to send from
Test, then publish
In the test panel, ask "Can you send a document for me?" If you are asked to connect, use the connection manager to sign in, then ask again
When it works, publish the agent, add the Teams and Microsoft 365 channel, and share the link from Availability options so people can add it in Teams
What Happened in Testing
Once the template existed, a single request sent it. The agent filled in the template, the subject ("Please sign immediately"), and the message, and the envelope arrived in the recipient's inbox moments later, ready to review and sign. Asking "Tell me about my Docusign" returned the account details, and asking about templates listed the template with its ID, dates, and page count.
None of that took code. The video compares it with a custom Power Automate flow built earlier for ServiceNow, which needed expressions and formulas just to update a record. With an MCP server, that layer is already done.
Where This Fits in a Business
Any team that sends agreements on a repeat basis can use this: offer letters in HR, NDAs and order forms in sales, leases in property management. A few choices make it safe to roll out:
Let templates do the governing. The agent sends only what your templates contain, so legal-approved wording stays intact
Turn on confirmation before sending, so a person approves each envelope
Each user connects with their own Docusign account, so the agent can only do what that person is already allowed to do, and Docusign keeps its usual record of who sent what
Start with a narrow job, like sending one type of agreement, and add more once people trust it
The same pattern works well beyond Docusign. More companies publish MCP servers all the time, and because MCP is an open standard, the same servers can also work with AI tools other than Copilot Studio. For a business, the more useful question is which repeat tasks are worth handing to an agent first.
Where to Take It Next
Give the agent instructions and a few starter prompts so people know what to ask, and add more MCP servers as your work needs them. If you have several agents like this, our post on multi-agent orchestration in Copilot Studio shows how to put one agent in front of all of them. What agreement would you send first?
Have a question or an idea for a future video? Leave a comment on the full video walkthrough on the Collaboration Simplified YouTube channel.
Contact Us
Questions? Reach out anytime.
Phone
© 2020–Present Collaboration Simplified. All rights reserved.
Collaboration Simplified® is a registered trademark of Shervin Shaffie.