How to Use the Adobe Sign MCP in Claude Code

Q: What is the command to install the Adobe Sign MCP Server in Claude Code?

Run claude mcp add --transport http adobe-sign -- . Make sure you place all flags before the server name.

Manage Adobe Sign workflows from your terminal. Claude Code executes contract generation and compliance checks as automated shell tasks.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Adobe Sign MCP to Claude Code

Create your Vinkius account to connect Adobe Sign to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Adobe Sign with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Trigger contracts from the MCP Server

Automating Adobe Sign vendor onboarding requires connecting isolated systems. Your terminal agent handles this by running `create_transient_document` right from a GitHub Action. It pushes the generated SLA document straight to the signing platform. The script then calls `create_agreement` to email the vendor. You get a fully automated pipeline that sends legally binding contracts the moment a new partner gets added to your database.

Audit permissions from the CLI

Security audits mean verifying exactly who has access to your Adobe Sign company templates. Instead of clicking through admin panels, run a quick terminal command. The agent uses `list_users` to dump every active account. It cross-references those users against your internal directory. By calling `list_groups`, the agent identifies anyone sitting in the wrong permission tier and flags them in your output logs.

Fetch compliance records headlessly

Sometimes you need to prove a specific deploy was authorized via Adobe Sign. Your CLI agent pulls the necessary paperwork using `get_agreement_audit_trail`. It downloads the certified PDF directly to your server. You can pipe this data straight into your archiving system. Calling `get_agreement_combined_document` grabs the actual signed files, letting your cron jobs back up critical contracts automatically every night via MCP.

Setup guide

Set up Adobe Sign MCP in Claude Code

Prerequisites

Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
Active Vinkius subscription with a valid endpoint token

1

Run the add command

Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.
2

Verify the connection

Start a Claude Code session and type /mcp to list connected servers. You should see adobe-sign-mcp with a green status indicator.
3

Start using tools

Ask Claude Code something like "Check my latest Adobe Sign transactions." It will automatically discover and invoke the available Adobe Sign tools.

Terminal

claude mcp add --transport http adobe-sign-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Get your connection token →

Prerequisites

Claude Code CLI installed
Active Vinkius subscription with a valid endpoint token

1

Open the config file

Create or edit .mcp.json in your project root for project-level scope, or ~/.claude.json for user-level scope.
2

Add the Adobe Sign MCP

Paste the JSON snippet shown on the right into the mcpServers object. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Restart Claude Code

Start a new Claude Code session. Type /mcp to confirm the server is connected. The tools will be automatically available in your conversation.

.mcp.json

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Adobe Sign. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Adobe Sign now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Adobe Sign MCP in Claude Code

Run `claude mcp add --transport http adobe-sign -- `. Make sure you place all flags before the server name.

Setting up event listeners is simple from the command line. The agent can list existing hooks and create new ones pointing to your production endpoints.

Ask the CLI to check the status of your contracts. It fetches the metadata and prints the outstanding signatures right in your terminal window.

Yes. You just need to pass your Vinkius auth token via environment variables. The headless agent handles the rest of the execution.

Vinkius processes your PDF binaries and webhook URLs in an isolated, ephemeral sandbox. The data passes directly to your local machine, leaving zero trace on the intermediary infrastructure.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript