DocuSign MCP connector
The DocuSign connector brings DocuSign users, contacts, permission profiles, templates, and billing invoices to Claude, ChatGPT, Cursor, Microsoft Copilot, and any MCP client, so each person works inside their own DocuSign access with every call logged.
- Connects over OAuth
- Free 14-day trial
- No credit card
List DocuSign users added to the Legal permission profile
Working in DocuSign with Elaichi
-
List all DocuSign users
-
Get single DocuSign user by ID
-
List all DocuSign contacts
How to connect DocuSign to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
DocuSign MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
DocuSign MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
DocuSign MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
DocuSign MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
DocuSign MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect DocuSign to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with DocuSign through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in DocuSign is logged.
-
IT
Set up a new hire in DocuSign
Create the DocuSign user, fill in their profile, and check which permission profile they have landed on, all from the same conversation where the onboarding ticket came in.
-
People
Close a leaver's DocuSign seat the same day
Look up the departing employee, confirm the account is theirs, and remove the DocuSign user so the seat is not paying for someone who has gone.
-
Legal
Find the right template before anyone sends
Ask which DocuSign templates exist for an NDA, an MSA, or an offer letter, and pull up the details of one to confirm it is the current approved version.
-
Sales
Keep signer contacts current after a call
When a buyer changes their email or a new signer joins the deal, update the DocuSign contact or add a new one without opening the address book by hand.
-
Finance
Check the DocuSign plan and latest invoice
Pull up the current DocuSign billing plan and recent invoices to answer a budget question or reconcile a charge, without asking the DocuSign admin for a screenshot.
-
Operations
Review who holds which DocuSign permissions
List every DocuSign user alongside their permission profile to spot people with more access than their role needs, and adjust the ones that are wrong.
Try asking
- “List DocuSign users added to the Legal permission profile”
- “Which DocuSign contacts have no assigned permission profile?”
- “Show custom settings for our DocuSign sales users”
What connecting DocuSign gets you
6 screens from Elaichi, each doing one job for your DocuSign account.
Ask Elaichi to work across your apps.
List DocuSign users added to the Legal permission profile
Which DocuSign contacts have no assigned permission profile?
Show custom settings for our DocuSign sales users
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about DocuSign users in plain language.
Three starter prompts return answers from live DocuSign users, contacts and permission profiles.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach DocuSign.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
70 DocuSign tools are ready to call.
Users, contacts, permission profiles and custom settings, with no custom code written.
Toolboxes
Each team gets its own DocuSign toolbox.
Curate separate toolboxes so Legal, Sales and IT see different DocuSign tools.
Shared connections
Teammates use DocuSign without seeing credentials.
Every connection shows who connected it and how many teams and members share it.
Audit log
Every DocuSign call is on the record.
When, who, what happened, type and resource for each user and contact change.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
DocuSign digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
DocuSign
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
DocuSign
Queued
Automations
A schedule drafts your DocuSign digest.
Six steps fetch users, group them, draft a digest, await approval, then post back.
DocuSign health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Contacts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Legal 34%
Sales EMEA 27%
IT Operations 21%
HR 18%
Collections and dashboards
DocuSign health arrives before anyone asks.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for DocuSign
All three can connect DocuSign to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over DocuSign tools | Allow or restrict single DocuSign tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per DocuSign call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
DocuSign tools for your AI agents
70 tools are ready to call through Elaichi's MCP endpoint the moment you connect DocuSign, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect DocuSign to Claude?
Connect DocuSign in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. DocuSign asks your organization to register an OAuth application inside DocuSign itself, so one administrator brings a client ID and secret across once when setting the connector up. After that, each person simply signs in to DocuSign in the browser the first time they use it, and nobody else ever handles those details.
Does DocuSign work with ChatGPT and Cursor as well as Claude?
Yes. Once DocuSign is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect DocuSign once and every client your team uses can reach it.
What can an AI agent actually do with my DocuSign data?
With DocuSign connected, an agent can add, update, and remove DocuSign users, look up which permission profile each person holds, and keep signer contacts current. It can also find the right DocuSign template, and pull up your billing plan and invoices for a finance question. Because DocuSign has a large number of actions available, short concrete asks like "list our DocuSign templates" tend to get better results than long multi-part requests.
Does connecting DocuSign give the AI access to everything in my account?
No. Every request to DocuSign runs as the person who signed in, so an agent can only see the users, contacts, templates, and billing details that person's own DocuSign permission profile already allows. Elaichi can narrow that access further by team or by action, but it can never widen it beyond what DocuSign itself grants that person.
Can I stop an agent from deleting or changing things in DocuSign?
Yes. In Elaichi you can restrict DocuSign actions individually, for example allowing agents to look up users and templates while restricting any action that deletes a DocuSign user or contact. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.
What happens to a DocuSign connection when someone leaves?
When you offboard someone in Elaichi, their access to DocuSign through every connected client ends at once. If they had shared a DocuSign connection with a team, it keeps working for everyone else, and disconnecting DocuSign once in Elaichi removes it from every client at the same time.
Does the DocuSign MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. DocuSign is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for DocuSign?
Yes. Both let Claude, ChatGPT or Cursor use DocuSign. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every DocuSign call.
How is Elaichi different from Composio for DocuSign?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to DocuSign: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put DocuSign in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot