How to Use the Yousign MCP in Claude Code

Q: How do I programmatically initiate a Yousign workflow using Claude Code?

You run createrequest from the terminal to start the draft. This action provides the unique request ID that your script needs to pass into every other tool call.

Q: Can I check the status of a Yousign request in Claude Code?

Yes, run getrequest and feed it the specific ID. This outputs the current state—whether it's pending, active, or canceled—directly to your standard output.

Q: What data does the Yousign MCP Server provide about document lists?

The server provides file metadata when you call listdocuments. This allows your shell script to verify the existence and names of attached documents as part of a pre-flight check.

Q: Does Yousign support adding signers via scripts in Claude Code?

Absolutely. You execute addsigner, giving it the request ID and the signer's contact details directly from your script arguments. It’s built for headless execution.

Q: What data type does this Yousign MCP Server touch regarding quotas?

It touches API consumption metrics via getconsumption. You run this command to check quota limits and ensure your automated CI/CD job won't fail due to over-usage.

Run Yousign eSignature Operations in Claude Code. Headless automation for CI/CD pipelines.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Yousign MCP to Claude Code

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

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Automating Request Initialization

Your shell script needs to start a signature process? Call `create_request` with a descriptive name. The output provides the ID you need immediately for subsequent steps in your CI/CD pipeline. If the job needs more people, use `add_signer`. You pass the request ID and contact details via environment variables or command arguments, making it perfect for automated deployment scripts.

Managing Signer Lifecycle

Scripts need to kill a process? Run `cancel_request` using the request ID. It’s clean, direct terminal action that permanently stops an ongoing workflow. Monitoring is key for DevOps. You can use `get_request` to check the status of any given signature ID at any point during your pipeline run.

Auditing and Listing Documents

Build a validation step that checks all documents attached to a process using `list_documents`. This is perfect for ensuring compliance before deployment. For comprehensive logging, use `list_requests` to dump every signature request in the organization into your log files. It gives you an instant audit trail of all activity.

Setup guide

Set up Yousign 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 yousign-mcp with a green status indicator.
3

Start using tools

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

Terminal

claude mcp add --transport http yousign-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 Yousign 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": {
    "yousign-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 Yousign. 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 Yousign 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 Yousign MCP in Claude Code

You run `create_request` from the terminal to start the draft. This action provides the unique request ID that your script needs to pass into every other tool call.

Yes, run `get_request` and feed it the specific ID. This outputs the current state—whether it's pending, active, or canceled—directly to your standard output.

The server provides file metadata when you call `list_documents`. This allows your shell script to verify the existence and names of attached documents as part of a pre-flight check.

Absolutely. You execute `add_signer`, giving it the request ID and the signer's contact details directly from your script arguments. It’s built for headless execution.

It touches API consumption metrics via `get_consumption`. You run this command to check quota limits and ensure your automated CI/CD job won't fail due to over-usage.

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