Adobe Acrobat Sign MCP Server for Cursor 10 tools — connect in under 2 minutes
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
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.
{
"mcpServers": {
"adobe-acrobat-sign": {
"url": "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.
Cursor's Agent mode turns Adobe Acrobat Sign into an in-editor superpower. Ask Cursor to generate code using live data from Adobe Acrobat Sign and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
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 Cursor 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 Cursor via MCP
Follow these steps to integrate the Adobe Acrobat Sign MCP Server with Cursor.
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
Save the file
Cursor will automatically detect the new MCP server
Start using Adobe Acrobat Sign
Open Agent mode in chat and ask: "Using Adobe Acrobat Sign, help me...". 10 tools available
Why Use Cursor with the Adobe Acrobat Sign MCP Server
Cursor AI Code Editor provides unique advantages when paired with Adobe Acrobat Sign through the Model Context Protocol.
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Adobe Acrobat Sign + Cursor Use Cases
Practical scenarios where Cursor combined with the Adobe Acrobat Sign MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Adobe Acrobat Sign MCP Tools for Cursor (10)
These 10 tools become available when you connect Adobe Acrobat Sign to Cursor 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 Cursor
Ready-to-use prompts you can give your Cursor agent to start working with Adobe Acrobat Sign immediately.
"Show me all agreements waiting for signature"
Troubleshooting Adobe Acrobat Sign MCP Server with Cursor
Common issues when connecting Adobe Acrobat Sign to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Adobe Acrobat Sign + Cursor FAQ
Common questions about integrating Adobe Acrobat Sign MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.Can Cursor use MCP tools in inline edits?
How do I verify MCP tools are loaded?
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 Cursor
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.