How do I get started with Adobe Sign?

Subscribe, then enter your Adobe Sign access token (from **Adobe Admin Console → Acrobat Sign → API → Integration Key**). Your AI agent connects instantly to the global v6 API. No code, no complex setup — just connect and start signing.

Can my AI agent send a contract for signature to multiple people?

Yes. Upload a document, then create an agreement with multiple signers in a specific order. Adobe Sign handles the sequential signing flow — Signer 1 gets notified first, then Signer 2 after completion, and so on. Your agent tracks each signer's progress in real time.

What if a signer hasn't signed yet — can I send a reminder?

Just tell your agent "send a reminder for the Acme NDA." It sends an email reminder to all pending signers with an optional custom message. No tab-switching, no logging into Adobe Sign — your agent handles it directly from your conversation.

Can I access the legal audit trail for compliance?

Yes. Every signed agreement has a tamper-proof audit trail showing exactly when it was created, viewed, signed, and by whom — with timestamps and IP addresses. Perfect for legal departments, regulated industries, and any business that needs proof of signing for compliance.

Adobe Acrobat Sign MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Adobe Acrobat Sign
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Adobe Acrobat Sign and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "adobe-acrobat-sign": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Adobe Acrobat Sign MCP Server

Connect your Adobe Acrobat Sign account to any AI agent and manage your entire e-signature workflow through natural conversation.

GitHub Copilot Agent mode brings Adobe Acrobat Sign data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Agreements — List, search, create, and cancel e-signature agreements
Signing Status — Track who has signed, who is pending, and send reminders to signers
Audit Trails — Access legally binding audit trails for any signed agreement
Library Documents — Browse reusable templates and library documents
Document Upload — Upload documents for signature via the transient document workflow
Participants — View all signers, approvers, and CC recipients with their status

The Adobe Acrobat Sign MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Adobe Acrobat Sign to VS Code Copilot via MCP

Follow these steps to integrate the Adobe Acrobat Sign MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Adobe Acrobat Sign

Ask Copilot: "Using Adobe Acrobat Sign, help me...". 10 tools available

Why Use VS Code Copilot with the Adobe Acrobat Sign MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Adobe Acrobat Sign through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Adobe Acrobat Sign + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Adobe Acrobat Sign MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Adobe Acrobat Sign MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Adobe Acrobat Sign to VS Code Copilot via MCP:

adobe_agreement_members

Returns each member email, role (SIGNER/APPROVER/ACCEPTOR/FORM_FILLER/DELEGATE_TO_SIGNER/CC), and their signing status. Use to check who has signed, who is pending, or to review the signing workflow. Get all participants (signers, approvers, CC recipients) in a specific Adobe Sign agreement with their roles and status

adobe_audit_trail

The audit trail is a legally binding record of all actions taken: when the agreement was created, viewed, signed, and by whom (with IP addresses and timestamps). Essential for legal compliance and dispute resolution. Get the legal audit trail for an Adobe Sign agreement — a tamper-proof record of all signing events and actions

adobe_cancel_agreement

This is irreversible — the agreement cannot be re-sent (a new one must be created). An optional comment explains the cancellation reason to all participants. Use when a deal falls through, terms change, or the document needs to be replaced. Cancel an Adobe Sign agreement that is currently out for signature — stops the signing process and notifies all parties

adobe_create_agreement

Create a new Adobe Sign agreement and send it for signature — the core e-signature workflow for contracts, NDAs, and legal documents

adobe_get_agreement

Returns name, status, all participant sets with their roles (SIGNER/APPROVER/CC/DELEGATE), signature type, creation and modification dates, and any external IDs. Use after listing agreements to drill into a specific agreement for complete information. Get complete details of a specific Adobe Sign agreement by ID, including all participants, signing status, and document metadata

adobe_list_agreements

Returns agreement name, current status, signature type (ESIGN/WRITTEN), creator email, and creation/modification dates. Agreement statuses: DRAFT (being built), OUT_FOR_SIGNATURE (awaiting signatures), SIGNED (fully executed), CANCELLED, EXPIRED. Use when the user asks about pending signatures, completed agreements, or document pipeline. List Adobe Acrobat Sign agreements with name, status (DRAFT/OUT_FOR_SIGNATURE/SIGNED/CANCELLED/EXPIRED), sender, and dates

adobe_list_library_documents

Library documents are reusable templates that can be referenced when creating new agreements. Returns document name, ID (for use in adobe_create_agreement fileInfos), sharing mode, and creation date. Use when the user asks "what templates do we have?" or needs a library document ID. List reusable library documents (templates) in Adobe Sign — pre-built agreements, forms, and document templates

adobe_search_agreements

Returns matching agreements with names, statuses, and dates. Use when the user wants to find a specific agreement, look up a contract by name, or search across the document library. Search Adobe Sign agreements by name or keyword to find specific documents across your signature pipeline

adobe_send_reminder

The agreement must be in OUT_FOR_SIGNATURE status. An optional comment is included in the reminder email. Use when the user says "remind them to sign" or "send a reminder for the contract." Send a signing reminder to all pending signers on an Adobe Sign agreement — nudges recipients who have not yet signed

adobe_upload_document

Returns a transientDocumentId that is then used in adobe_create_agreement fileInfos. This is the standard workflow: (1) upload document → (2) create agreement with the transientDocumentId → (3) agreement is sent for signature. Upload a document to Adobe Sign as a transient document — the first step before creating an agreement for signature

Example Prompts for Adobe Acrobat Sign in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Adobe Acrobat Sign immediately.

"Show me all agreements waiting for signature"

Troubleshooting Adobe Acrobat Sign MCP Server with VS Code Copilot

Common issues when connecting Adobe Acrobat Sign to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Adobe Acrobat Sign + VS Code Copilot FAQ

Common questions about integrating Adobe Acrobat Sign MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.