Adobe Acrobat Sign MCP connector
The Adobe Acrobat Sign connector brings agreements, signed documents, audit trails and user accounts into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, with each person signing in as themselves and every call logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Which agreements are still waiting on a signer this week?
Working in Adobe Acrobat Sign with Elaichi
-
List all Adobe Acrobat Sign users
-
Get single Adobe Acrobat Sign user by ID
-
List all Adobe Acrobat Sign agreements
How to connect Adobe Acrobat Sign to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Adobe Acrobat Sign 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.
Adobe Acrobat Sign 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.
Adobe Acrobat Sign 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.
Adobe Acrobat Sign 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.
Adobe Acrobat Sign 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 Adobe Acrobat Sign 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 Adobe Acrobat Sign through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Adobe Acrobat Sign is logged.
-
Sales
Check where a contract stands before the call
Ask which agreements are still waiting on a signer, pull the current status of a specific deal's contract, and cancel one that went to the wrong person.
-
Legal
Pull the signed copy and its audit trail
Get the combined signed document and the full audit trail for any agreement the moment a question comes up, without digging through the Adobe Acrobat Sign account.
-
HR
Set up and retire signer accounts
Create an Adobe Acrobat Sign user for a new hire, put them in the right group, and deactivate the account on their last day.
-
Procurement
Hand an agreement to a new owner
When a buyer changes roles, change the sender on their open vendor agreements so contracts keep moving, and tidy up who each agreement is shared with.
-
Finance
Find signed agreements for close and audit
List which agreements completed this month, fetch each signed PDF, and confirm who signed what and when from the audit trail.
-
Operations
Keep the user list in order
List every Adobe Acrobat Sign user, fix locales and group memberships in one pass, and spot accounts nobody is using.
Try asking
- “Which agreements are still waiting on a signer this week?”
- “Pull the signed copy and audit trail for the Northwind MSA.”
- “Create a user for Priya and add her to the Legal group.”
What connecting Adobe Acrobat Sign gets you
6 screens from Elaichi, each doing one job for your Adobe Acrobat Sign account.
Ask Elaichi to work across your apps.
Which agreements are still waiting on a signer this week?
Pull the signed copy and audit trail for the Northwind MSA.
Create a user for Priya and add her to the Legal group.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about agreements in plain language.
Which contracts are still unsigned, who signed last week, answered from live Adobe Acrobat Sign records.
Copy the endpoint
AI apps
One endpoint reaches Adobe Acrobat Sign everywhere.
Claude, ChatGPT and Cursor share one governed endpoint, with no SDK and no shared API key.
Tool catalog
185 Adobe Acrobat Sign tools, no code.
Agreements, signed documents, audit trails, users and groups, covered without writing a line of code.
Toolboxes
Every team gets its own toolbox.
Legal sees audit trails, Sales sees agreement status, HR manages users, each scoped to its team.
Shared connections
Share the connection, never the API key.
One person connects Adobe Acrobat Sign and teammates work through it without seeing a credential.
Audit log
Know who touched every agreement.
When, who, what happened and which agreement, in a log that cannot be edited.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Adobe Acrobat Sign digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch agreements
Adobe Acrobat Sign
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
Adobe Acrobat Sign
Queued
Workflows
A schedule starts the work, you approve it.
Every Monday, unsigned agreements are fetched, grouped, drafted into a digest, approved, then posted back.
Adobe Acrobat Sign health
Refreshed 4 minutes ago · every 15 minutes · from the agreements collection
Agreements
1,284 ↓ 12%
Documents
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Agreements created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Legal 27%
HR 21%
Procurement 18%
Collections and dashboards
Agreement numbers arrive without anyone asking.
Agreements created over 14 days, split by team, computed without a model and refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Adobe Acrobat Sign
All three can connect Adobe Acrobat Sign 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 Adobe Acrobat Sign tools | Allow or restrict single Adobe Acrobat Sign 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 Adobe Acrobat Sign 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.
Adobe Acrobat Sign tools for your AI agents
185 tools are ready to call through Elaichi's MCP endpoint the moment you connect Adobe Acrobat Sign, 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 Adobe Acrobat Sign to Claude?
Connect Adobe Acrobat Sign in Elaichi by pasting its API key, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. There is no OAuth application to register in Adobe Acrobat Sign and no client ID or secret to generate. Once Claude is connected, sign in to Elaichi as yourself and start asking about agreements.
Does Adobe Acrobat Sign work with ChatGPT and Cursor as well as Claude?
Yes. Adobe Acrobat Sign is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. Nothing is set up again per client.
What can an AI agent actually do with my Adobe Acrobat Sign data?
It can list your Adobe Acrobat Sign agreements and tell you which are waiting on a signer, fetch the signed document or its audit trail, cancel an agreement, change who the sender is, and manage user accounts, groups and locales. Short, concrete asks such as 'which agreements are still unsigned this week' work better than long paragraphs.
Does connecting Adobe Acrobat Sign give the AI access to every agreement in my account?
No. Each person signs in to Elaichi as themselves, so the agent only sees the agreements, users and groups that person can already see in Adobe Acrobat Sign. Elaichi can narrow that access with roles and restrictions, and it never widens it.
Can I stop an agent from canceling or changing agreements in Adobe Acrobat Sign?
Yes. Restrictions in Elaichi work per action, so you can allow reading Adobe Acrobat Sign agreements while restricting canceling them, changing the sender or deactivating users, and set the restriction on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to an Adobe Acrobat Sign connection when someone leaves?
Offboarding the person in Elaichi ends their access to Adobe Acrobat Sign through every client at once. A shared connection keeps working for everyone else on the team. If you want the connector gone entirely, disconnecting Adobe Acrobat Sign once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the Adobe Acrobat Sign MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Adobe Acrobat Sign 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 Adobe Acrobat Sign?
Yes. Both let Claude, ChatGPT or Cursor use Adobe Acrobat Sign. 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 Adobe Acrobat Sign call.
How is Elaichi different from Composio for Adobe Acrobat Sign?
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 Adobe Acrobat Sign: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Adobe Acrobat Sign 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