How to Use the Eversign (Cloud Electronic Signature) MCP in Claude

Q: How do I install the Eversign (Cloud Electronic Signature) MCP server in Claude Desktop?

Open your claudedesktopconfig.json file via the developer settings. Add the server command and arguments under the mcpServers object, then restart the application.

Q: Can Claude Desktop trigger an Eversign (Cloud Electronic Signature) template?

Yes. Your agent uses the createdocument tool to reference an existing template ID. It passes the signer names and emails directly into the API request.

Generate contracts, pull business IDs, and manage e-signatures directly inside Claude Desktop without touching a browser.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Eversign (Cloud Electronic Signature) MCP to Claude Desktop

Create your Vinkius account to connect Eversign (Cloud Electronic Signature) to Claude Desktop 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 Eversign (Cloud Electronic Signature) with Claude Desktop

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Map your accounts with Claude Desktop

The `list_businesses` tool lets Claude check your account and grab the exact business_id required for any contract operation. You ask your agent to prepare a signing workflow, and it automatically queries the endpoint to figure out which tenant or sub-account you want to target. Finding these IDs manually usually means digging through settings pages. Now, your local AI client reads the available businesses and stores the reference ID in context. That keeps the subsequent API calls properly routed without you copy-pasting alphanumeric strings.

Draft and send contracts via MCP Server

Calling `create_document` allows your agent to push out fresh agreements or build reusable templates on the fly. You hand Claude a text file from your local machine, and it formats the payload to generate a legally binding signature request. It handles the routing for existing templates just as easily. If you already have an NDA template saved in Eversign, Claude triggers it with specific signer details, bypassing the web dashboard entirely.

Connect local files to cloud signatures

Combining `list_businesses` and `create_document` gives your desktop agent full control over the e-signature lifecycle. You can drop a PDF into your Claude chat, and the MCP connection handles the business routing and document creation in one shot. This setup bridges your local filesystem with the remote signing service. The AI client reads your draft, builds the API request, and returns the tracking link right in your conversation.

Setup guide

Set up Eversign (Cloud Electronic Signature) MCP in Claude Web or Desktop

1

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
2

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.
3

Start a conversation

Open a new chat. The Eversign (Cloud Electronic Signature) MCP tools are available immediately — no restart needed.

Endpoint URL

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

No configuration file needed — paste the URL directly in the Claude web interface.

Available on Free (1 connector), Pro, Max, Team, and Enterprise plans.

Prerequisites

Claude Desktop installed (macOS or Windows)
Active Vinkius subscription with a valid endpoint token

1

Open Claude Desktop Settings

Click the menu icon at the top-left corner, go to Settings → Developer → Edit Config. This opens claude_desktop_config.json in your default text editor.
2

Paste the Eversign (Cloud Electronic Signature) MCP configuration

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

Restart Claude Desktop

Close and reopen the application. Claude needs a full restart to load new MCPs — refreshing a conversation is not enough.
4

Verify the connection

Open a new conversation. Click the 🔌 icon at the bottom of the message input. You should see tools listed under eversign-cloud-electronic-signature-mcp.

json

{
  "mcpServers": {
    "eversign-cloud-electronic-signature-mcp": {
      "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 Eversign. 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 Eversign (Cloud Electronic Signature) 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 Eversign (Cloud Electronic Signature) MCP in Claude Desktop

Open your claude_desktop_config.json file via the developer settings. Add the server command and arguments under the mcpServers object, then restart the application.

Yes. Your agent uses the create_document tool to reference an existing template ID. It passes the signer names and emails directly into the API request.

Every document operation requires a specific business ID to route the request correctly. The tool fetches this automatically so you avoid manual lookups in your account settings.

Yes. You can ask Claude to read a local contract draft and then push it to the signing service using the document creation tool.

Vinkius runs this integration in an ephemeral V8 Isolate Sandbox. When your agent processes e-signature requests or reads document templates, the data passes through a zero-trust environment that drops all memory the moment the transaction completes.

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