Adobe Acrobat Sign to MCP: Agreements, Signers, Signed PDFs and Templates in any AI Agent

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Adobe Acrobat Sign, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Adobe Acrobat Sign

Adobe Acrobat Sign REST API v6, signed in as an Acrobat Sign user: find agreements and check who has signed, read participants, events, form data, signing links, the signed PDF and audit trail, send documents or library templates for signature, send reminders, and browse templates, web forms, users, groups, workflows and webhooks. Cancelling agreements installs switched off.

Setup

Setting up takes about 15 minutes. You need an Acrobat Sign account (Business, Enterprise or a free developer account for testing) and an account admin who creates the API application.

1. Sign in to Acrobat Sign as an account admin and note your shard from the browser address: https://secure.na1.adobesign.com/... means na1; the others are na2, na3, na4, eu1, eu2, jp1, au1, in1 and sg1. Put only the shard code into ADOBE_SIGN_SHARD.
2. Open Account, Acrobat Sign API, API Applications, click +, enter a name and a display name and choose the domain CUSTOMER.
3. Select the new application and click Configure OAuth for Application. Set the Redirect URI to https://cloud.anythingmcp.com/api/mcp-oauth/callback on AnythingMCP Cloud, or <your AnythingMCP URL>/api/mcp-oauth/callback when you host AnythingMCP yourself. It must be https and match exactly.
4. On the same page enable the scopes user_read, agreement_read, agreement_write, agreement_send, library_read, widget_read, workflow_read and webhook_read. Pick the modifier self for a personal connector; account admins may pick account to reach every user's agreements (see Scopes below). Save.
5. Click View/Edit on the application and copy the Application ID into ADOBE_SIGN_CLIENT_ID and the Client Secret into ADOBE_SIGN_CLIENT_SECRET. Install the connector.
6. On the connector page click Authorize with Provider and sign in to Acrobat Sign. Then run adobe_acrobat_sign_get_base_uris: apiAccessPoint must contain your shard. If it shows another one, correct ADOBE_SIGN_SHARD and authorize again.

Scopes: the connector asks for user_read agreement_read agreement_write agreement_send library_read widget_read workflow_read webhook_read, which means the :self modifier: the signed-in user's own agreements, templates and web forms. An account admin who wants the AI to see the whole account changes them in the connector's OAuth settings to agreement_read:account, user_read:account and so on (the same modifiers must be enabled on the application) and authorizes again. adobe_acrobat_sign_list_users needs user_read:account.

Tokens: access tokens last one hour and are renewed automatically through /oauth/v2/refresh on your shard. A refresh token that is not used for 60 days expires; then click Authorize with Provider again.

What it reads: agreements, listed newest first or searched by text (names, participant emails and names, messages, external ids, field content) with filters for status, role, type, created or modified date and participant email; one agreement with sender, participant sets, cc list, message, dates and source documents; the members of an agreement and the step each one is at; the audit events (created, sent, viewed, signed, delegated, reminder sent, completed); the values entered in form fields; the signing links of the participants who must act now; the documents of an agreement; the agreement as one PDF, as a temporary link or as a file, and the audit trail report as a PDF file; reminders; library documents (reusable templates) with their form fields; web forms with their public URL, settings, entered data and the agreements they created; users, groups and group members; custom send workflows; webhooks.

What it writes: adobe_acrobat_sign_upload_transient_document fetches a file (PDF, Word, Excel, image) from a URL and uploads it, up to 10 MB; transient documents expire after 7 days. adobe_acrobat_sign_create_agreement creates an agreement from a transient document, a library template or a public file URL: with state IN_PROCESS it is sent at once, DRAFT keeps it unsent and AUTHORING lets the sender place fields in Acrobat Sign first. adobe_acrobat_sign_send_agreement sends a DRAFT or AUTHORING agreement, and adobe_acrobat_sign_create_reminder reminds participants who have not acted yet, once or on a schedule. These tools are on at install, and sending and reminders email real people, so the AI shows you the documents, the recipients in order and the message and sends only after a clear yes.

Creating an agreement: file_infos takes one entry per document, a transientDocumentId, a libraryDocumentId or a urlFileInfo with url, name and mimeType that Adobe fetches itself. participant_sets lists the recipients with order (1, 2, ...) and role (SIGNER, APPROVER, ACCEPTOR, FORM_FILLER, CERTIFIED_RECIPIENT). Without signature fields in the document (text tags or template fields), Acrobat Sign adds a signature block at the end. merge_field_info pre-fills template fields by name; adobe_acrobat_sign_list_library_document_form_fields shows the names.

Switched off at install: adobe_acrobat_sign_cancel_agreement, because a cancelled agreement cannot be signed any more and the cancellation cannot be undone. An admin switches it on when the team needs it.

Data formats: agreement status is OUT_FOR_SIGNATURE, OUT_FOR_APPROVAL, SIGNED, APPROVED, ACCEPTED, FORM_FILLED, DELIVERED, CANCELLED, EXPIRED, DRAFT, AUTHORING and a few more. Member status such as WAITING_FOR_MY_SIGNATURE, NOT_YET_VISIBLE or COMPLETED shows each participant's step. Dates are ISO 8601 in UTC. Form data comes as CSV text; only the sender can read it, by default only for completed agreements. PDFs from adobe_acrobat_sign_download_combined_document and adobe_acrobat_sign_download_audit_trail are handed over as file attachments, up to 10 MB. Signing links become available a few seconds after sending.

Paging: list tools return page.nextCursor, which the AI passes as cursor until it is missing. adobe_acrobat_sign_search_agreements pages with start_index (from searchPageInfo.nextIndex), up to 100 results per page and 10,000 in total.

Limits: Acrobat Sign throttles API calls per user and per account depending on the plan; a 429 answer carries Retry-After in seconds.

Common errors: 401 INVALID_ACCESS_TOKEN means the authorization expired or was revoked: authorize again. A 401 right after authorizing usually means a wrong ADOBE_SIGN_SHARD. 403 PERMISSION_DENIED or INVALID_API_ACCESS_POINT means a scope or its modifier is missing (for example user_read:account for users), the user may not see that agreement, or the call went to the wrong shard. 404 INVALID_AGREEMENT_ID or another INVALID_..._ID means a wrong id, or an agreement of another user while the scope is :self. 400 INVALID_ARGUMENTS, MISSING_REQUIRED_PARAM or INVALID_EMAIL names the field that is missing or wrong. 404 AGREEMENT_NOT_EXPOSED on signing links means the agreement is still being prepared: wait a few seconds and ask again.

The connector does not create or change library templates, web forms, workflows, webhooks, users or groups, and it deletes nothing.

Prerequisites: ADOBE_SIGN_SHARD, ADOBE_SIGN_CLIENT_ID, ADOBE_SIGN_CLIENT_SECRET

Install the connector locally

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Open http://localhost:3000/connectors/store, pick Adobe Acrobat Sign and paste in the env vars listed under Prerequisites.

Available tools

Example prompts

• "Which agreements have been out for signature for more than a week, and who still has to sign each one?"
• "Download the signed PDF and the audit trail of the NDA with Example Ltd."
• "Send the library template Mutual NDA to [email protected] for signature, with me as the second signer. Show me everything before sending."
• "Remind the participants who have not signed the Q4 supplier contract yet."
• "Show the data people entered in the Event Registration web form as a table."

Next steps

• Connect to Claude
• Connect to ChatGPT