# 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.

Source: https://elaichi.ai/connectors/adobesign/

## Facts

| | |
| --- | --- |
| Application | Adobe Acrobat Sign |
| Category | Cloud Storage |
| AI tools | 185 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Adobe Acrobat Sign is connected

- 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.

## Connect Adobe Acrobat Sign in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Adobe Acrobat Sign.
2. Optionally set Share with, then press Connect.
3. Paste an Adobe Acrobat Sign API key. One person generates a token in Adobe Acrobat Sign and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Adobe Acrobat Sign tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Adobe Acrobat Sign MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Adobe Acrobat Sign MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Adobe Acrobat Sign tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Adobe Acrobat Sign through Elaichi

### Check where a contract stands before the call

Sales. 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.

### Pull the signed copy and its audit trail

Legal. 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.

### Set up and retire signer accounts

HR. Create an Adobe Acrobat Sign user for a new hire, put them in the right group, and deactivate the account on their last day.

### Hand an agreement to a new owner

Procurement. 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.

### Find signed agreements for close and audit

Finance. List which agreements completed this month, fetch each signed PDF, and confirm who signed what and when from the audit trail.

### Keep the user list in order

Operations. List every Adobe Acrobat Sign user, fix locales and group memberships in one pass, and spot accounts nobody is using.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Adobe Acrobat Sign connection?

Yes. One person connects Adobe Acrobat Sign with the API key and shares the connection with a team, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every request.

### 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.

## All 185 Adobe Acrobat Sign tools

Every tool below is callable through https://api.elaichi.ai/mcp once Adobe Acrobat Sign is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Adobe Acrobat Sign users** (List). Retrieves all the users in an account.
- **Get single Adobe Acrobat Sign user by ID** (Get). Retrieves detailed information about the user in the caller account.
- **Adobe Acrobat Sign users update state** (Update). Activate/Deactivate a given user. Required: state, user_id.
- **Update a Adobe Acrobat Sign user by ID** (Update). Update an user. Required: accountType, isAccountAdmin, id, email, status.
- **Adobe Acrobat Sign users update groups** (Update). Updates the groups of the user. Required: groupInfoList, user_id.
- **Adobe Acrobat Sign users update locale** (Update). Updates the user locale. Required: user_id.
- **Adobe Acrobat Sign users create view** (Create). Retrieves the URL of manage, account settings and user profile page. Required: name, user_id.
- **Create a Adobe Acrobat Sign user** (Create). Creates a new user in the Acrobat Sign system Required: accountType, isAccountAdmin, id, email, status.
- **List all Adobe Acrobat Sign agreements** (List). Retrieves agreements for the user.
- **Get single Adobe Acrobat Sign agreement by ID** (Get). Retrieves the current status of an agreement.
- **Adobe Acrobat Sign agreements get combined document** (Get). Retrieves a single combined PDF document for the documents associated with an agreement. Required: agreement_id. Returns a binary file.
- **Adobe Acrobat Sign agreements delete shares** (Delete). Delete an agreement share. Required: deleteAgreementSharesInfo, agreement_id.
- **Adobe Acrobat Sign agreements get combined document pages info** (Get). Retrieves info of all pages of a combined PDF document for the documents associated with an agreement. Required: agreement_id.
- **Adobe Acrobat Sign agreements get combined document URL** (Get). Retrieves url of all visible pages of all the documents associated with an agreement. Required: agreement_id.
- **Adobe Acrobat Sign agreements update visibility** (Update). Updates the visibility of an agreement. Required: visibility, agreement_id.
- **Adobe Acrobat Sign agreements update sender** (Update). This API can change sender for an agreement that has status of draft Required: senderId, agreement_id.
- **Adobe Acrobat Sign agreements get settings** (Get). Get the settings for the agreement Required: agreement_id.
- **Adobe Acrobat Sign agreements update vaulted** (Update). Complete the vaulting process and update the agreement as vaulted. Required: vaultEventId, agreement_id.
- **Adobe Acrobat Sign agreements get me** (Get). Retrieves the agreement information related to the api caller Required: agreement_id.
- **Adobe Acrobat Sign agreements get documents image URLS** (Get). Retrieves image urls of all visible pages of all the documents associated with an agreement. Required: agreement_id.
- **Adobe Acrobat Sign agreements create view** (Create). Retrieves the latest state view url of agreement. Required: name, agreement_id.
- **Adobe Acrobat Sign agreements update state** (Update). Updates the state of an agreement identified by agreementId in the path. This endpoint can be used by originator/sender of an agreement to transition between the states of agreement. An allowed transition would follow the… Required: state, agreement_id.
- **Adobe Acrobat Sign agreements get audit trail** (Get). Retrieves the audit trail of an agreement identified by agreementId. PDF file stream containing audit trail information Required: agreement_id. Returns a binary file.
- **Update a Adobe Acrobat Sign agreement by ID** (Update). Updates the draft agreement or update the expiration of an existing in progress agreement. Required: signatureType, participantSetsInfo, name, fileInfos, status.
- **Adobe Acrobat Sign agreements create deliverable access** (Create). Generates URL or AccessCode for each participant of an agreement. Linkless notification feature needs to be enabled specifically for generating AccessCode(s). Required: accessType, participantAccessInfos, agreement_id.
- **Adobe Acrobat Sign agreements delete documents** (Delete). Deletes all the documents of an agreement. Required: agreement_id.
- **Adobe Acrobat Sign agreements get form fields merge info** (Get). Retrieves the merge info stored with an agreement. Required: agreement_id.
- **Adobe Acrobat Sign agreements update form fields merge info** (Update). Set the merge info for an agreement. Required: agreement_id.
- **Adobe Acrobat Sign agreements share** (Share). Share an agreement with someone. Required: shareCreationInfo, agreement_id.
- **Adobe Acrobat Sign agreements create signer identity report** (Create). Retrieves the signer identity report of an agreement identified by agreementId. PDF file stream containing signer identify information Required: agreement_id. Returns a binary file.
- **Adobe Acrobat Sign agreements copy** (Copy). Create a copy of an existing agreement (POST /agreements/{id}/copy), optionally with a new name, state (DRAFT to copy without sending), documents and recipients. Required: agreement_id.
- **Adobe Acrobat Sign agreements get form data** (Get). Retrieves data entered into the interactive form fields of the agreement. This API can only be called by the creator of the agreement Required: agreement_id.
- **Adobe Acrobat Sign agreements get signing URLS** (Get). Retrieves the URL for the e-sign page for the current signer(s) of an agreement. Fetches the URL for the e-sign page for the current signer, optionally including the saved signature from the signer's profile if present. Required: agreement_id.
- **Create a Adobe Acrobat Sign agreement** (Create). Creates an agreement. Sends it out for signatures, and returns the agreementID in the response to the client. This is a primary endpoint which is used to create a new agreement. An agreement can be created using… Required: state, signatureType, participantSetsInfo, name, fileInfos.
- **Adobe Acrobat Sign agreements mobile focus** (Action). Create a mobilefocus specification for agreements. Required: agreement_id.
- **Adobe Acrobat Sign agreements create form fields** (Create). Adds template fields to an agreement Required: templateId, agreement_id.
- **Adobe Acrobat Sign agreements get form fields** (Get). Retrieves details of form fields of an agreement. Required: agreement_id.
- **Adobe Acrobat Sign agreements update form fields** (Update). Updates form fields of an agreement. Form fields generated by text tags and FormFieldGenerators are not available to be modified until the agreement has been placed in AUTHORING mode. Required: fields, agreement_id.
- **Adobe Acrobat Sign agreements get note** (Get). Retrieves the latest note associated with an agreement. Required: agreement_id.
- **Adobe Acrobat Sign agreements update note** (Update). Updates the latest note associated with an agreement. Required: note, agreement_id.
- **List all Adobe Acrobat Sign library documents** (List). Retrieves library documents for a user.
- **Get single Adobe Acrobat Sign library document by ID** (Get). Retrieves the details of a library document.
- **Adobe Acrobat Sign library documents create view** (Create). Retrieves the latest state view url of a library document. Required: name, library_document_id.
- **Update a Adobe Acrobat Sign library document by ID** (Update). Updates the library document. Currently status, name, sharingMode and templateTypes of the library document can only be updated. Required: sharingMode, templateTypes, name, fileInfos, status.
- **Adobe Acrobat Sign library documents get audit trail** (Get). Retrieves the audit trail associated with a library document. Required: library_document_id. Returns a binary file.
- **Adobe Acrobat Sign library documents get form fields** (Get). Retrieves details of form fields of a library document. Required: library_document_id.
- **Adobe Acrobat Sign library documents update form fields** (Update). Updates details of form fields of a library document. When enabled for the account, if a field is required and its contentType is not DATA or CALC, assignee must be specified and cannot be null; otherwise the request fails… Required: fields, library_document_id.
- **Adobe Acrobat Sign library documents get combined document URL** (Get). Retrieves url of all visible pages of all the documents associated with a library document. Required: library_document_id.
- **Adobe Acrobat Sign library documents get me** (Get). Retrieves the library document information related to the api caller Required: library_document_id.
- **Adobe Acrobat Sign library documents update visibility** (Update). Updates the visibility of library document. Required: visibility, library_document_id.
- ...and 135 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
