4,500+ servers built on MCP Fusion
Vinkius

Yousign MCP. Manage document signatures via conversation.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Yousign MCP on Cursor AI Code Editor MCP Client Yousign MCP on Claude Desktop App MCP Integration Yousign MCP on OpenAI Agents SDK MCP Compatible Yousign MCP on Visual Studio Code MCP Extension Client Yousign MCP on GitHub Copilot AI Agent MCP Integration Yousign MCP on Google Gemini AI MCP Integration Yousign MCP on Lovable AI Development MCP Client Yousign MCP on Mistral AI Agents MCP Compatible Yousign MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

Yousign connects your AI agent directly to your eSignature workflow. You can manage document requests, add signers, check status updates, and audit usage—all through simple conversation.

It's for legal teams who need total control over the entire signature lifecycle without logging into a dashboard.

What your AI agents can do

Activate request

Activates a draft signature request and sends automated email notifications to all assigned signers.

Add signer

Adds new signer contact details to an existing, drafted signature request using the provided Request ID.

Cancel request

Permanently stops an ongoing signature process. You must provide both the Request ID and a reason for cancellation.

+ 5 more capabilities included
Initiate new signature workflows

The agent creates a draft request record in Yousign so you can begin adding documents or signers.

Add and update signer details

You specify the Request ID and contact info, and the agent adds one or more people as required signatories to an existing workflow.

Track request status changes

The system retrieves the current state of any specific signature process, showing if it's drafted, ongoing, done, or cancelled. This uses get_request.

View all active and past requests

You get a list of every document request within your organization, allowing you to find IDs or status summaries for multiple processes at once.

Review attached documents

The agent lists every file linked to a specific signature request so you can confirm the right documents are attached before activation.

Check API usage and quotas

You retrieve your current API consumption metrics, seeing how many signatures remain on your plan via get_consumption.

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

Yousign MCP Server: 8 Tools for Document Workflow

Use these eight tools to manage the full lifecycle of electronic signatures—from creating drafts to auditing consumption—all through your AI agent.

activate019d7626

activate request

Activates a draft signature request and sends automated email notifications to all assigned signers.

add019d7626

add signer

Adds new signer contact details to an existing, drafted signature request using the provided Request ID.

cancel019d7626

cancel request

Permanently stops an ongoing signature process. You must provide both the Request ID and a reason for cancellation.

create019d7626

create request

Creates a brand new, draft signature request record in your Yousign account using a descriptive name.

get019d7626

get consumption

Retrieves detailed information on your API usage and remaining credit count for the current billing period.

get019d7626

get request

Pulls all details and real-time status updates for one specific signature request ID.

list019d7626

list documents

Lists every file attached to a specified signature request, allowing verification before activation.

list019d7626

list requests

Returns a comprehensive list of all signature requests across your entire Yousign organization.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Yousign, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 4,700+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week

What you can do with this MCP connector

Listen up. Forget logging into some clunky eSignature dashboard. You're gonna connect Yousign straight to your AI agent, and you’ll manage the entire document signature lifecycle using plain conversation. This lets you handle everything—from setting up a new request to auditing who signed what—without ever clicking a button.

Starting a Workflow

Need a contract signed? You're gonna start by creating a brand-new, draft signature request record in your Yousign account using the create_request tool; this gives you an immediate ID and name for that workflow. If you need to see what other requests are floating around, you can pull a comprehensive list of everything across your whole organization with list_requests.

To check out every single document attached to one specific request before you hit send, use list_documents on the relevant Request ID.

Populating and Customizing Requests

Once that draft is live, you'll need people and documents. You can expand an existing workflow by using the add_signer tool; just give your agent the specific Request ID and the new person’s contact details, and they add them as a required signatory. If you mess up or need to change things, you can permanently stop any process that's going sideways with cancel_request, but remember: you gotta provide both the Request ID and a solid reason why it's being canceled.

Sending and Tracking Status

You’re ready to go. You activate the draft request—which sends automated email notifications out to every assigned signer—by calling activate_request. When you need to know where things stand, you don't guess. For real-time updates on one specific signature process, get_request pulls all the details and current state: is it drafted? Is it ongoing? Is it done?

If you want a full picture of your usage, run get_consumption. This tool retrieves detailed metrics on your API usage and tells you exactly how many signatures you've got left for this billing period.

How It Works in Practice

It’s simple. You hook up the Yousign MCP Server to your AI client. Then, you just talk to it. You tell your agent what job needs doing—like 'Add John Smith to contract XYZ' or 'What's the status of Request ID 123?' The agent runs the precise tool, gets the data back from Yousign, and gives you the straight answer you need.

It’s total control, zero dashboard clicking.

How Yousign MCP Works

  1. 1 First, you subscribe to the server and input your Yousign API Key into your client.
  2. 2 Next, you tell your agent what needs doing. For example: 'Create a new request for the Q3 Vendor Agreement.'
  3. 3 The agent runs the appropriate tool (e.g., create_request), sends you the result (a Request ID), and then uses that ID to perform follow-up actions like adding signers or checking status.

The bottom line is: your AI client handles all API calls, so you manage complex signing processes using plain chat commands instead of clicking through web dashboards.

Who Is Yousign MCP For?

Legal Counsel and Compliance Officers who spend too much time checking status pages. It's for the HR Manager stuck manually updating contracts or the Sales Professional needing to activate a deal immediately without navigating five different screens.

Legal Operations Specialist

Uses list_requests and get_request constantly. They need an instant audit trail of which documents are pending signatures, who failed to sign, and why.

Human Resources Manager

Automates the onboarding signing process. They use the agent to add multiple new employees as signers via add_signer right after creating a contract draft.

Sales Director

Needs immediate visibility into deal closure. They check status using get_request to confirm if an active client has signed the final agreement.

What Changes When You Connect

  • Control the full signing lifecycle. Instead of navigating multiple screens, you use create_request to draft a contract and add_signer to assign recipients—all in one chat session.
  • Get instant status updates. Don't wonder if a document was signed. Use get_request to check real-time status (draft, ongoing, done) without logging into the dashboard.
  • Audit your limits instantly. Running out of signatures shouldn't surprise you. Use get_consumption to see exactly how many credits you have left in the billing cycle.
  • Keep workflows moving when they stall. If a contract is stuck, use cancel_request with a reason to officially halt it and document why it failed or was aborted.
  • Verify documents before sending. Use list_documents on any request ID to see exactly which files are attached, preventing accidental sends with the wrong paperwork.

Real-World Use Cases

01

Contract Renewal Oversight

The Ops Manager needs to know how many agreements are pending renewal. They ask their agent: 'List all requests for vendor contracts.' The agent runs list_requests and gives a count, saving the manager from clicking through hundreds of records.

02

Urgent Deal Activation

A Sales Professional just finalized a deal. They need to get it signed now. Instead of manual steps, they ask the agent to 'Activate request ID req-105.' The agent runs activate_request, sending all necessary email notifications instantly.

03

Debugging a Failed Signature

The Legal team notices a contract failed. They use their agent to run get_request on the specific ID, getting immediate details on why it stalled and which signers were responsible for the failure.

04

Compliance Cleanup

A department merge requires halting old agreements. The Compliance Officer asks: 'Cancel all requests older than 90 days.' The agent runs cancel_request on those IDs, permanently stopping the process and logging the reason.

The Tradeoffs

Manually tracking document IDs

Trying to remember or manually search for a specific Request ID (like req-102) across different tabs and dashboards is tedious and error-prone.

Use list_requests first. This pulls all necessary request IDs into one list, letting your agent find the exact record you need before running get_request.

Assuming status from memory

Thinking a contract is 'done' because it was signed last week, but failing to check if there are follow-up tasks or necessary audits.

Always verify the current state using get_request and cross-reference attached files with list_documents. This confirms the full scope of completion.

Ignoring usage limits

Starting a massive campaign without realizing you've hit your monthly signature quota, leading to failure mid-process.

Always check your capacity first. Use get_consumption right at the start of any major signing operation.

When It Fits, When It Doesn't

Use this MCP Server if your team needs total control over the lifecycle of a document—from creation and adding signers to activation, monitoring status, and cancellation. If you are managing compliance workflows or high-volume contracts, this is for you.

Don't use this if you simply need to view stored documents that aren't part of a signature process (use a standard file storage tool instead). Also, don't rely on it just for basic list views; always follow up with get_request or list_documents to confirm the current state. This server is about actions and state transitions, not passive data retrieval.

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.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 8 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

activate_request add_signer cancel_request create_request get_consumption get_request list_documents list_requests

Checking document status shouldn't require four different tabs.

Today, checking if a contract moved from 'Drafting' to 'Pending Signatures' means logging into the Yousign portal. You click the list view, search by name, open the request, then check sub-tabs for signer status, and finally review attached documents just to verify what's there. It takes time, and you risk missing a crucial detail.

With this MCP server, your AI agent handles all that navigation. You simply ask: 'What is the status of the vendor agreement?' The agent runs `get_request`, pulling real-time data—signer list, current state, and document count—and gives it to you in one clean reply.

Yousign MCP Server: Full control over signing workflows.

Manual steps that vanish include clicking 'Add Signer' on the dashboard, navigating away to find their email, and then clicking 'Activate' when ready. Each step is a point of failure or delay.

Now, you tell your agent: 'First, add Jane Smith (jane@company.com) as a signer to req-101, then activate it.' The agent executes the sequence (`add_signer` then `activate_request`) in rapid succession. It's immediate workflow execution.

Common Questions About Yousign MCP

How do I list all ongoing signature requests using Yousign MCP Server? +

Use list_requests. This function pulls a list of every document request in your organization, giving you the IDs and basic statuses needed to know what's active.

What is the difference between `get_request` and `list_requests`? +

list_requests gives you an overview of all requests. get_request pulls deep, real-time details for one specific request ID only, giving you the current state of every signer involved.

Can I check my Yousign API quota with the MCP Server? +

Yes. Run get_consumption. This tool retrieves your exact API usage and remaining credit count so you never run out of signatures unexpectedly.

How do I permanently stop a signing process using Yousign MCP Server? +

Use cancel_request. You must provide the Request ID and specify a mandatory reason for cancellation. This ensures the action is auditable.

How do I use the `list_documents` tool to verify files attached to a request? +

list_documents shows every file connected to a specific signature request. You provide the request ID, and your agent returns a list of all associated documents. This lets you confirm contents before activating or sending out the contract.

What is the proper sequence for starting a new signing workflow using `create_request`? +

create_request puts everything in draft mode. You run this first to establish the request and give it a name. After that, you'll use other tools like add_signer and then activate_request to finalize the process.

Does `add_signer` require full contact details for every signer? +

Yes, add_signer needs the request ID plus specific contact details for the person. Providing accurate information here ensures your agent can correctly add them to the existing draft signing process.

What does running `activate_request` actually do to a pending signature workflow? +

activate_request changes the request status from draft to active. More importantly, it triggers email notifications automatically, sending the signed document out to all assigned signers.

Can I check the status of a signature request via chat? +

Yes. The get_signature_request tool allows your AI agent to retrieve the real-time status of any request ID, showing you whether it is in 'draft', 'ongoing', 'done', or has been 'cancelled'.

How do I add signers to a draft request using the agent? +

You can use the add_signer tool. Provide the unique request ID along with the signer's email, first name, and last name. You can add multiple signers to a single request before activating it.

Can I see how many signature credits I have left in my plan? +

Absolutely. Use the get_api_consumption tool to retrieve your current usage statistics and remaining signature credits, helping you manage your Yousign subscription budget.

You might also like

Built & Managed by Vinkius 30s setup 8 tools

We've already built the connector for Yousign. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 8 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.