SignRequest MCP for AI. Automate Document Signing Workflows by Conversation.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
How this MCP server connects to your AI agent
SignRequest lets you automate e-signatures and handle full document lifecycles via your AI client. It creates signing requests using templates, tracks signers in real time, and manages all associated documents—from initial creation to final webhook notification.
You can manage users, teams, and custom webhooks directly from conversation.
What AI agents can do with SignRequest Automation
Create document
Creates a brand-new document in SignRequest when given a file URL or template UUID and required signers.
Create signrequest
Starts the official process of sending out a signing request for an existing document.
Create webhook
Registers and sets up a new webhook URL, allowing instant notifications when specific events happen in SignRequest.
Builds a new document using either an uploaded file URL or a saved template UUID, assigning required signers.
Sends out a formal signing request for an existing document and tracks its status until completion.
Fetches specific documents or entire sign requests by their unique UUID to check progress or details.
Creates and manages webhooks, ensuring your internal systems get real-time notifications for signing events (e.g., signature complete).
Retrieves lists of organizational users, teams, and available templates to control access and document structure.
Ask an AI about this
Waiting for input…
What AI agents can do with SignRequest: 12 Tools for Document & Workflow Ops
These twelve tools let you perform every critical action needed for document lifecycle management—from listing users to setting up automated webhook triggers.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using SignRequest on VinkiusCreate Document
Creates a brand-new document in SignRequest when given a file URL or template UUID and required signers.
Create Signrequest
Starts the official process of sending out a signing request for an existing...
Create Webhook
Registers and sets up a new webhook URL, allowing instant notifications when...
Delete Document
Permanently removes a document from your account using its UUID.
Get Document
Retrieves the full details of a single, specific document by providing its unique...
Get Signrequest
Fetches all information about a specific signing request using its UUID, including signer status and progress.
Get Template
Retrieves the details of an existing document template by providing its unique UUID.
List Documents
Returns a list of all documents associated with your SignRequest account.
List Teams
Retrieves a directory listing of the teams configured within your organization's...
List Templates
Lists all available, reusable document templates you have saved in the system.
List Users
Retrieves a list of every user account managed by your organization's SignRequest...
List Webhooks
Lists all webhooks you have registered, allowing you to see their current status and destination URLs.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
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.
Start a conversation
Open a new chat. The SignRequest integration is available immediately — no restart needed.
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
Make Your AI Do More
Start with SignRequest, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ 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
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by SignRequest. 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
Built on the Model Context Protocol (MCP) for 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 connection provides 12 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Tracking contracts shouldn't mean opening 5 different dashboards., Solved with Vinkius AI Gateway
Today, tracking one contract means jumping between the CRM to see who was assigned, the email system to find the attached draft, and finally logging into SignRequest just to check if the signer opened it. You spend more time coordinating status reports than closing deals.
With this MCP server, you simply ask your agent: 'Where are we with the Acme contract?' The agent runs `get_signrequest` and gives you a single, definitive answer in plain language. It’s one prompt; zero dashboard switching.
SignRequest MCP Server: Automate signing status reporting.
Manual processes currently require copying the document UUID and then pasting it into a separate system just to verify its current state. This is tedious, error-prone copy/paste work that slows down your entire pipeline.
Now, you ask the agent for status. It uses `get_document` or `get_signrequest` and reports back the data directly in the conversation flow. The process runs instantly, giving you a clear answer every time.
What your AI can actually do with this
Look, you don't want to jump between tabs or copy UUIDs just to get a signature. This server connects your AI client directly into SignRequest, letting you run whole document workflows using plain language commands. It handles everything from building the initial paperwork to making sure your internal systems know the second someone signs off.
Managing Your Workspace and Users
Want to see what's going on? You can pull a list of every user account managed in your organization by calling list_users. Similarly, if you need an overview of organizational units, use list_teams to grab all the configured teams. To make sure everyone has the right access and structure, you can also run list_templates, which gives you a roster of every reusable document template you've saved in the system.
Building and Getting Documents
To start fresh, you can build a brand-new document using create_document. You just gotta feed it either an uploaded file URL or a specific template UUID, and tell it who needs to sign. If you need details on one of those saved templates before building, use get_template with its unique UUID.
To get the full scoop on any existing paperwork, run get_document, feeding it the document's UUID for all the deep details.
When a document is done and needs to be wiped, you can delete it permanently using delete_document and the UUID. If you just need a simple inventory of everything floating around your account, list_documents gives you that list right away.
Running the Signing Workflow
Got a document ready? You'll use create_signrequest to kick off the official signing process for an existing file. This starts tracking the entire thing until it’s done. To check up on where things stand, you can pull all info about one specific request using get_signrequest, which shows you who signed and how far along everyone is.
If you need to verify a single document's status or details after sending out the request, use get_document again.
Automating Notifications (Webhooks)
Here's where the automation kicks in. You don't want to manually check for signatures; you wanna be notified instantly. To set that up, call create_webhook, giving it a URL so SignRequest can ping your systems when something happens—like someone signing or declining.
Need to see what webhooks are already running? Use list_webhooks to pull the list of all registered endpoints and check their current status and destination URLs. If you're debugging, run list_webhooks to get that full picture.
The Bottom Line: What You Can Do
You can use get_template by UUID to grab template details; you'll also need it for the create_document call. To manage your setup completely, run list_users, list_teams, and then check out all available templates with list_templates. If you want a list of every document associated with your account, list_documents provides that overview.
This collection lets you initiate the entire lifecycle: you build the paperwork (create_document), send it out (create_signrequest), track its status using UUIDs (get_signrequest, get_document), and connect it all to your other systems with webhooks. It's a complete loop, man.
019e5d55-b302-7073-bf99-5ee1672ac44a 
Here's how it actually works
The bottom line is you talk to your AI client, and it handles all the API calls required to manage signatures for you.
Subscribe to the SignRequest server and provide your API Key.
Your AI client authenticates with Vinkius using the key. The agent can then call specific tools like list_users or get_template.
You ask your agent a natural language query (e.g., 'Send this NDA to Jane Doe'). The agent formats and executes the necessary tool calls (create_signrequest) in sequence.
Who is this actually for?
Legal Counsel who hates chasing down signed contracts. Sales Operations staff tired of manual contract delivery. HR Administrators who need to automate offer letters and compliance paperwork. If your job involves tracking documents that change hands, this is for you.
Uses create_signrequest to send out NDAs or agreements using standardized templates (get_template), and then uses list_documents to check the status of every outstanding contract.
Automates sending sales agreements via create_document for new clients, and sets up webhooks (create_webhook) so their CRM instantly knows when a deal is signed.
Uses list_users to confirm who needs access, then executes document creation (create_document) for new hires using standard offer letter templates, all without leaving their desk.
What Changes When You Connect
Track signers live. When you run get_signrequest, you don't guess status; you see exactly who has signed, who is pending, and when they need to act.
Build workflows without manual data entry. Use create_document with templates or URLs—the agent handles the setup for new contracts so you just give a prompt.
Get notified instantly. Setting up webhooks via create_webhook means your CRM updates automatically the second an agreement is signed, eliminating delays and status checks.
Manage permissions easily. The ability to run list_users or list_teams lets your agent verify if a user has the right access before trying to send them a sensitive contract.
Centralize governance. You can list every document (list_documents) or template (list_templates) in one place, giving you clear oversight of your entire digital filing system.
See it in action
Onboarding a New Employee
The HR admin needs to get three documents signed (NDA, offer letter, policy agreement). Instead of opening the template for each and manually adding signers, they ask their agent: 'Send the standard onboarding package for John Doe.' The agent uses create_document multiple times with templates and assigns all necessary roles. They then use get_signrequest to track progress until everything is complete.
Automating Sales Pipeline Milestones
A sales rep needs the signing status of a client's agreement to update their internal project board. Instead of checking the SignRequest portal, they ask: 'What's the latest on Acme Corp contract?' The agent runs get_signrequest and reports back the current status (e.g., 'Pending Legal Review'), allowing the rep to move the deal forward immediately.
Compliance Cleanup
The compliance officer needs to retire old, unused templates for regulatory reasons. They ask: 'List all templates that haven't been used in six months.' The agent runs list_templates and the officer can then use delete_document on specific UUIDs to clear out stale data.
System Integration Hookup
The development team needs their billing system to know when a contract is finalized. They ask the agent to 'Set up a webhook for signing completion.' The agent uses create_webhook and provides the necessary endpoint, linking document status directly into external business processes.
The honest tradeoffs
Thinking documents are static files
Manually downloading a PDF from SignRequest, editing it in Adobe, and re-uploading it. This loses the audit trail and requires manual status tracking.
Always start with get_template or create_document. Use those tools to ensure you are working with the correct version and that all signing metadata is preserved.
Checking status by guessing UUIDs
Trying to find a document by remembering vague details (e.g., 'the one for Smith last week'). This wastes time searching through emails.
First, run list_documents or list_users to get an overview. Then, use the UUIDs returned in those lists with get_document or get_signrequest for precise data retrieval.
Ignoring system notifications
Having to log into SignRequest every hour just to see if someone signed the contract, leading to missed follow-ups.
Set up a webhook using create_webhook. This sends an immediate notification to your internal systems the moment the signature status changes.
When It Fits, When It Doesn't
Use this server if your primary bottleneck is moving contracts from 'Draft' to 'Signed.' It handles creation, delivery, tracking, and integration triggers. Don’t use it if you need a specialized legal review workflow that requires human judgment—the tools provide the mechanisms (e.g., create_signrequest), but external logic must enforce complex approval chains. If your main goal is just storing documents without formal signing requirements, consider a simple file storage service instead of this full workflow suite.
Questions you might have
How do I start a signing request using create_signrequest? +
You initiate it by providing the document's UUID or a template UUID. The agent handles the rest, setting up the formal workflow and notifying the signers immediately.
Can I list all my current contracts with list_documents? +
Yes, list_documents pulls a full inventory of every document in your account. You can then ask for details on specific ones using their UUIDs.
What is the difference between get_document and get_signrequest? +
get_document retrieves the file/metadata itself (the contract). get_signrequest tracks the process of signing—who signed it, when they signed it, and its current status.
How do I connect my external system to know when a document is signed? +
You use create_webhook. This tool registers a URL on your side. When the signing event happens in SignRequest, it sends an instant notification payload to that URL.
How do I manage user access and verify team membership using list_users or list_teams? +
You use list_users to pull a roster of all accounts associated with your SignRequest workspace. This tool lets you check who has access and helps confirm which teams are active before initiating any signing workflow.
What is the best way to find or validate existing document structures using list_templates? +
list_templates pulls a full catalog of your reusable legal templates, giving you their UUIDs. You should run this first whenever you need to create a new contract because it verifies which pre-built structure you're working with.
If I no longer need a document and want to delete it completely, how do I use delete_document? +
delete_document removes a file by its UUID from your account. Use this only when you are absolutely sure the document is outdated or sensitive data needs permanent removal.
When should I call create_document versus waiting until I run create_signrequest? +
You use create_document to prepare and build a raw file first. You must successfully generate the document before you can pass it off using create_signrequest to actually start the signing process.
Can I check the current status and signers of a specific document? +
Yes! Use the get_document tool with the document's UUID. The agent will return the document's status, signer details, and other metadata.
How do I see which reusable templates are available in my account? +
Simply ask the agent to run the list_templates action. It will provide a list of all configured templates that you can use to create new documents.
Is it possible to automate notifications when a document is signed? +
Yes, you can use the create_webhook tool to register a URL that will receive real-time notifications for events like document_signed or signer_signed.
We've already built the connector for SignRequest. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 12 tools are live and waiting.
You're up and running in seconds.
Gemini 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.
Built, hosted, and secured by Vinkius. You just connect and go.