How to Use the eSignly Electronic Signature MCP in Claude Code

Q: How do I add the eSignly Electronic Signature MCP server to Claude Code?

Run claude mcp add --transport http esignly -- in your terminal. Replace with the server endpoint from Vinkius. Use claude mcp list to confirm it was added correctly.

Q: Can I check my eSignly account status from the command line?

Yes. After setting up the server, run claude exec esignly getesignlyaccountmetadata. It will print a JSON object with your account's metadata and current limits.

Q: How can I script a daily report of signed documents with eSignly Electronic Signature and Claude Code?

Use the listsuccessfullysigneddocuments tool in a shell script. You can run claude exec esignly listsuccessfullysigneddocuments and pipe the output to jq for parsing or save it to a file.

Q: What's the command to get an audit trail for a document with eSignly Electronic Signature and Claude Code?

The command is claude exec esignly listdocumentaudittrail --documentid='doc123'. Replace 'doc123' with your actual document ID to get the full JSON audit log.

Automate eSignly compliance checks and document reporting directly from your terminal with Claude Code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect eSignly Electronic Signature MCP to Claude Code

Create your Vinkius account to connect eSignly Electronic Signature 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 eSignly Electronic Signature with Claude Code

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Run Audits in Your CI/CD Pipeline

This MCP server is built for automation. Set up a nightly cron job or a step in your CI pipeline to verify document integrity. No browser or UI required. A simple shell script can call `list_successfully_signed_documents` to get a list of completed contracts. Then, pipe those IDs to another command that runs `list_document_audit_trail` for each one, appending the results to a compliance log file.

Terminal-Based Status Reporting

Get quick answers from your command line. You don't need a full application to check on a contract. Just use Claude Code and standard shell tools. Chain commands to get what you need, fast. Run `claude exec esignly list_esign_documents | grep 'pending'` to find waiting documents, then use `get_document_detailed_data` with a specific ID for more info. It's a direct, scriptable way to work.

Sync Data with Other Systems

Use this MCP connection as a bridge. You can easily pull data from eSignly and push it into other systems using simple scripts. It turns the API into a command-line utility. For example, run `claude exec esignly list_esign_contacts` and pipe the JSON output to a script that updates your local database. You can do the same thing to sync templates by calling `list_esign_templates`.

Setup guide

Set up eSignly Electronic Signature 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 esignly-electronic-signature-mcp with a green status indicator.
3

Start using tools

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

Terminal

claude mcp add --transport http esignly-electronic-signature-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 eSignly Electronic Signature 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": {
    "esignly-electronic-signature-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 eSignly Electronic Signature. 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 eSignly 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 eSignly Electronic Signature MCP in Claude Code

Run `claude mcp add --transport http esignly -- ` in your terminal. Replace `` with the server endpoint from Vinkius. Use `claude mcp list` to confirm it was added correctly.

Yes. After setting up the server, run `claude exec esignly get_esignly_account_metadata`. It will print a JSON object with your account's metadata and current limits.

Use the `list_successfully_signed_documents` tool in a shell script. You can run `claude exec esignly list_successfully_signed_documents` and pipe the output to `jq` for parsing or save it to a file.

The command is `claude exec esignly list_document_audit_trail --document_id='doc_123'`. Replace 'doc_123' with your actual document ID to get the full JSON audit log.

It is. The server only has access to document metadata, such as signer lists and event timestamps, never the file contents. Each API call you make runs in a separate, sandboxed process that is torn down immediately after, ensuring no data persists.

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