Cloud Storage
DocuSign MCP connector
The DocuSign connector brings DocuSign users, contacts, permission profiles, templates, and billing invoices to Claude, ChatGPT, Cursor, and any MCP client, so each person works inside their own DocuSign access with every call logged.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
69 tools
How to connect
How to connect DocuSign to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect DocuSign once
-
Open Connections, choose Add connection, and pick DocuSign.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own DocuSign app, then approve. DocuSign needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
Egnyte
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect DocuSign to 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.
Connect DocuSign to 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 today. The plugin directory lives at chatgpt.com/plugins.
Connect DocuSign to 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.
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.
Use cases
What teams do with DocuSign through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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”
AI tools
DocuSign tools for your AI agents
69 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.
See it in Elaichi
What connecting DocuSign gets you
6 screens from the product, each doing one job for your DocuSign account.
The agent
Ask about DocuSign users in plain language.
Three starter prompts return answers from live DocuSign users, contacts and permission profiles.
- users
- contacts
- permission profiles
- custom settings
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor reach DocuSign.
One org MCP endpoint over OAuth, no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
69 DocuSign tools are ready to call.
Users, contacts, permission profiles and custom settings, with no custom code written.
- List all DocuSign users
- Get single DocuSign user by ID
- Create a DocuSign user
- Update a DocuSign user by ID
ElaichiToolsToolboxes
Each team gets its own DocuSign toolbox.
Curate separate toolboxes so Legal, Sales and IT see different DocuSign tools.
- Legal
- Sales
- IT Operations
- HR
ElaichiToolboxesShared connections
Teammates use DocuSign without seeing credentials.
Every connection shows who connected it and how many teams and members share it.
- Legal
- Sales EMEA
- IT Operations
- HR
ElaichiConnectionsAudit log
Every DocuSign call is on the record.
When, who, what happened, type and resource for each user and contact change.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts your DocuSign digest.
Six steps fetch users, group them, draft a digest, await approval, then post back.
DocuSign digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
DocuSign
Queued
Collections and dashboards
DocuSign health arrives before anyone asks.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 blocking any action that deletes a DocuSign user or contact. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client at all, so no prompt, however worded, can reach it.
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.
Put DocuSign in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.