4,500+ servers built on MCP Fusion
Vinkius

Modusign MCP. Track signatures, audit history, and manage contracts via chat.

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

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

Just plug in your AI agents and start using Vinkius.

Modusign connects your AI agent to electronic contract management. Track document status, request signatures from templates, audit full document histories, and manage organization folders—all via natural conversation.

You can list contracts, check metadata, or initiate new signing workflows without leaving your chat tool.

What your AI agents can do

Create document from template

Creates an entirely new document instance using a specified contract template ID.

Get audit logs

Retrieves the full, time-stamped history of actions taken on a specific document.

Get document

Fetches all metadata and current status details for a single contract ID.

+ 7 more capabilities included
List Documents

Retrieves a list of all active electronic contracts, including their current status (signed, pending) and key identifiers.

Get Specific Document Details

Fetches complete metadata for a single document ID, giving you the full context without needing to guess which contract it is.

Audit Document History

Retrieves detailed audit logs showing who accessed the document and when, providing necessary compliance trail data.

List Templates

Shows all pre-defined contract templates available in your account, so you know what documents you can reuse.

Create Signature Requests

Generates a new document and sends out a signature request using an existing template ID and recipient email address.

View Organization Structure

Accesses folder and organizational metadata, allowing you to categorize and locate specific contract types.

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

Modusign MCP Server: 10 Tools for Document Operations

These ten tools allow your AI agent to manage every aspect of the document lifecycle—from listing contracts to requesting signatures and retrieving audit logs.

create019d75d7

create document from template

Creates an entirely new document instance using a specified contract template ID.

get019d75d7

get audit logs

Retrieves the full, time-stamped history of actions taken on a specific document.

get019d75d7

get document

Fetches all metadata and current status details for a single contract ID.

get019d75d7

get org info

Retrieves high-level organizational structure data, including account and user groupings.

list019d75d7

list automations

Lists all currently configured automated workflows for signature processing.

list019d75d7

list documents

Provides a list of every electronic contract in the account and their current status.

list019d75d7

list external files

Shows external documents that have been linked or attached to contracts.

list019d75d7

list folders

Lists the folder structure within your account, helping you navigate and locate document groupings.

list019d75d7

list templates

Shows a list of reusable contract templates available for creating new documents.

list019d75d7

list webhooks

Displays all active webhooks configured to trigger actions on document events.

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 Modusign, 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

You connect your AI agent directly to Modusign. You ditch the web interface and manage every contract lifecycle event—from finding a template to auditing who signs it—all through natural conversation with your client. It’s like having an instant, hyper-aware paralegal sitting right in your chat window.

When you need to know what documents exist or check their status, you don't guess. You just ask your agent to run list_documents, and it hands back a list of every electronic contract currently active, showing you the key identifiers and whether they’re signed or still pending.

Need to start fresh? You can first use list_templates to see all the reusable contracts your organization uses. Once you pick one, calling create_document_from_template instantly builds a brand-new document instance based on that template ID. That's it—you’ve created the draft.

To get granular, if you know a contract's unique ID, running get_document pulls all the metadata and the current status for that single file. It gives you the whole picture without making you jump through hoops or guessing which document you meant to ask about. You can also use list_external_files if you need to see any documents attached or linked outside of Modusign's core system.

When compliance matters, your agent doesn't just give you the current status; it digs deep into history using get_audit_logs. This tool retrieves a full, timestamped record detailing exactly who accessed the document and when they did it. It builds that necessary compliance trail right out to you.

Want context on how your whole account is set up? You can run list_folders to map out your organizational structure or call get_org_info to pull high-level data about user and account groupings. These tools help you categorize and locate specific types of contracts.

For process management, if you want to see what automation is running in the background for signatures, use list_automations. You can also check on any configured system triggers by calling list_webhooks, which shows every webhook set up to fire an action when a document event happens. Finally, your agent keeps tabs on how Modusign works behind the scenes, giving you access to list_templates and helping you see what existing contract templates are ready for reuse.

How Modusign MCP Works

  1. 1 Subscribe to the Modusign server and provide your API Key.
  2. 2 Ask your AI agent for a specific action (e.g., 'List all contracts needing signatures').
  3. 3 The agent calls the necessary tool (list_documents or get_document) and delivers the structured data directly into your chat interface.

The bottom line is: you manage entire contract workflows without ever leaving your primary chat window.

Who Is Modusign MCP For?

Legal and HR professionals, or Operations managers who spend time tracking down signatures and auditing compliance. This is for the person sick of switching between CRM dashboards, document storage portals, and email threads just to know if a contract was signed. You need an immediate, conversational source of truth.

Legal Counsel

Uses get_audit_logs to verify who accessed sensitive agreements and when, building compliance records instantly.

HR Operations Specialist

Runs checks on employee contracts using list_documents to see which new hires still have pending signature requests for onboarding paperwork.

Sales Account Manager

Uses the agent to create and send out standard NDAs (create_document_from_template) directly from a chat tool during a deal negotiation.

What Changes When You Connect

  • Get immediate status updates on all contracts. Instead of logging into the document portal, ask your agent to list_documents and see which agreements are pending signature right now.
  • Streamline contract creation. Use create_document_from_template to generate a new NDA instantly from an existing template ID and send it out—no manual steps needed.
  • Improve compliance visibility. When you need proof of access, run the get_audit_logs tool on any document ID to pull a complete, timestamped activity record immediately.
  • Stay organized with folder structure. Use list_folders to understand how your documents are grouped and use get_org_info for high-level account context without guessing where something lives.
  • Cut down on process time. Monitor automated workflows by running list_automations, ensuring that the system is correctly set up before you even ask for a signature.

Real-World Use Cases

01

The Board Meeting Check-in

A manager needs to know which board members signed the latest bylaws. Instead of emailing three different people, they prompt their agent: 'Show me the status for all board contracts.' The agent runs list_documents and provides a summary showing exactly who has signed and who hasn't.

02

Onboarding New Hires

An HR specialist needs to process 15 new employee agreements. They use the agent to call list_templates, select 'Standard Employment Agreement', and then run create_document_from_template for all 15 people, sending them out in bulk.

03

Post-Discovery Compliance Audit

A legal team must prove a client viewed a specific agreement last month. They feed the document ID into the agent and ask to get_audit_logs. The agent returns the full history, proving access times accurately.

04

Revising Standard Contracts

A sales team needs a new vendor agreement that follows standard policy. They use list_templates to find the right base contract, then call create_document_from_template, and send it out for immediate review.

The Tradeoffs

Treating documents like emails

Trying to track a signed contract by searching the document title or sender address. This is vague, prone to human error, and requires multiple manual searches across different platforms.

Use list_documents first. This command gives you a structured list of all contracts with their definitive status and ID, letting you narrow down your search immediately.

Guessing the document's history

Assuming that because an agreement exists, you know when it was reviewed or who opened it. This is a bad assumption for compliance reasons.

You must use get_audit_logs with the specific Document ID. The tool gives you the definitive timeline of events (creation, send date, open time).

Building contracts from scratch

Manually typing out clauses or starting a new document without using established company standards. This risks non-compliance and inconsistency.

Always use the list_templates tool to find your existing, approved templates. Then, run create_document_from_template to ensure brand consistency.

When It Fits, When It Doesn't

Use this server if your primary pain point is keeping track of document status and signing workflows across multiple people or departments. You need a single API entry point that handles the full lifecycle: listing, inspecting details (get_document), generating new requests, and auditing history (get_audit_logs).

Don't use this if your core need is pure storage management (e.g., just uploading files without workflow triggers) or if you only deal with simple file sharing that requires no formal audit trail. If you simply need to manage internal file permissions, a standard cloud drive API might be sufficient. However, when the transaction involves signing and compliance, Modusign is necessary.

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Modusign. 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 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

create_document_from_template get_audit_logs get_document get_org_info list_automations list_documents list_external_files list_folders list_templates list_webhooks

Checking contract status shouldn't require jumping between five tabs.

Today, checking a simple contract status means logging into your CRM to see the deal stage. Then you have to open the dedicated signing portal (a whole new tab). You check if it's signed there, then maybe jump back to email just to confirm who was supposed to sign next. It’s tedious and easy to miss an update.

With this MCP server, you simply ask your agent: 'What is the status of the Acme Corp agreement?' The agent calls `list_documents` or `get_document`, pulls all the current data—signed, pending, etc.—and gives it back in one direct answer. No tabs needed.

Modusign MCP Server: Manage contracts and signatures directly.

Manual contract fulfillment requires coordinating emails, tracking versions manually, and compiling audit reports from different systems. You spend hours just collating the 'proof' of what happened.

Now, you can use `get_audit_logs` to pull a complete record of every interaction with a document ID instantly. It’s definitive proof without any manual data gathering.

Common Questions About Modusign MCP

How do I check if all my contracts are signed using list_documents? +

You run list_documents. The tool returns a status column for every contract ID. You can filter the output directly from your agent to see only those marked 'Pending Signature'.

Can I send out a signature request using create_document_from_template? +

Yes, you pass an existing template ID and the recipient's email address. The tool handles creating the document instance and initiating the signing workflow in one step.

What is the difference between get_document and list_documents? +

Use list_documents when you want a broad overview of your entire contract portfolio. Use get_document when you already have a specific document ID and need all its detailed metadata.

How do I find out who touched a contract before it was signed? Use get_audit_logs. +

You provide the Document ID to get_audit_logs. The tool returns every user action (view, comment, edit) tied to that specific document's timeline.

Using `list_folders`, how can I map out the folder hierarchy for my documents? +

It returns a structured list of all document folders in your account. This lets you see where different contract types are stored, helping you keep related agreements grouped together without manually browsing.

What information does `list_webhooks` provide about active integrations? +

This tool shows the details of every webhook that is currently running. You can confirm which external systems are set up to receive status changes, like when a document moves from 'Pending' to 'Signed'.

Before I use `create_document_from_template`, how can I view all available types with `list_templates`? +

list_templates gives you a full list of every contract format you own. This confirms the template ID and name you need to reference before initiating a new signature request.

When I use `get_document`, what specific metadata fields does it retrieve for deep inspection? +

It pulls comprehensive data points beyond just status, including full audit trails, creation timestamps, and associated IDs. This is crucial if you need to verify the document's entire history.

Can I see who has already signed a document? +

Yes. Use the get_document tool with the specific Document ID. The agent will return the list of participants and their respective signing status.

What is an audit log in Modusign? +

An audit log records every action taken on a document, including when it was sent, opened, and signed, providing legal proof of the transaction. Use the get_audit_logs tool to retrieve this history.

How do I reuse my existing contract templates? +

Use the list_templates tool to find the Template ID you need, and then provide that ID to the create_document_from_template tool along with the signer's details.

You might also like

Built & Managed by Vinkius 30s setup 10 tools

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

No hosting. No infrastructure. No complex setup.
All 10 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.