Adobe Acrobat Sign MCP Server for Claude Code 10 tools — connect in under 2 minutes
Claude Code is Anthropic's agentic CLI for terminal-first development. Add Adobe Acrobat Sign as an MCP server in one command and Claude Code will discover every tool at runtime. ideal for automation pipelines, CI/CD integration, and headless workflows via Vinkius.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
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.
# Your Vinkius token. get it at cloud.vinkius.com
claude mcp add adobe-acrobat-sign --transport http "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
* 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.
Claude Code registers Adobe Acrobat Sign as an MCP server in a single terminal command. Once connected, Claude Code discovers all 10 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Adobe Acrobat Sign data drives decisions without human intervention.
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 Claude Code 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 Claude Code via MCP
Follow these steps to integrate the Adobe Acrobat Sign MCP Server with Claude Code.
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
Add the MCP Server
Run the command above in your terminal
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
Start using Adobe Acrobat Sign
Ask Claude: "Using Adobe Acrobat Sign, show me...". 10 tools are ready
Why Use Claude Code with the Adobe Acrobat Sign MCP Server
Claude Code provides unique advantages when paired with Adobe Acrobat Sign through the Model Context Protocol.
Single-command setup: `claude mcp add` registers the server instantly. no config files to edit or applications to restart
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
Claude Code runs headlessly, enabling unattended batch processing using Adobe Acrobat Sign tools in cron jobs or deployment scripts
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
Adobe Acrobat Sign + Claude Code Use Cases
Practical scenarios where Claude Code combined with the Adobe Acrobat Sign MCP Server delivers measurable value.
CI/CD integration: embed Adobe Acrobat Sign tool calls in your deployment pipeline to validate configurations or fetch secrets before shipping
Headless batch processing: schedule Claude Code to query Adobe Acrobat Sign nightly and generate reports without human intervention
Shell scripting: pipe Adobe Acrobat Sign outputs into other CLI tools for data transformation, filtering, and aggregation
Infrastructure monitoring: run Claude Code in a cron job to query Adobe Acrobat Sign status endpoints and alert on anomalies
Adobe Acrobat Sign MCP Tools for Claude Code (10)
These 10 tools become available when you connect Adobe Acrobat Sign to Claude Code 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 Claude Code
Ready-to-use prompts you can give your Claude Code agent to start working with Adobe Acrobat Sign immediately.
"Show me all agreements waiting for signature"
Troubleshooting Adobe Acrobat Sign MCP Server with Claude Code
Common issues when connecting Adobe Acrobat Sign to Claude Code through the Vinkius, and how to resolve them.
Command not found: claude
npm install -g @anthropic-ai/claude-codeConnection timeout
Adobe Acrobat Sign + Claude Code FAQ
Common questions about integrating Adobe Acrobat Sign MCP Server with Claude Code.
How do I add an MCP server to Claude Code?
claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.Can Claude Code run MCP tools in headless mode?
How do I list all connected MCP servers?
claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.Connect Adobe Acrobat Sign with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Adobe Acrobat Sign to Claude Code
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.