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.

Modusign MCP Server for Cursor 10 tools — connect in under 2 minutes

Name: Modusign
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 10 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Modusign and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "modusign": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Modusign MCP Server

Connect your Modusign account to your AI agent and streamline your document signing workflows through natural conversation.

Cursor's Agent mode turns Modusign into an in-editor superpower. Ask Cursor to generate code using live data from Modusign and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

What you can do

Document Tracking — List all electronic contracts and get real-time status updates (e.g., signed, pending).
Deep Inspection — Fetch complete metadata and audit trails for specific documents using their IDs.
Template Management — List your pre-defined contract templates for quick reuse.
Signature Requests — Create new signature requests from templates with a simple natural language command.
Automation & Webhooks — Monitor your automated signature workflows and active webhooks.
Org Structure — Access folders and organization metadata to keep your documents organized.

The Modusign MCP Server exposes 10 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Modusign to Cursor via MCP

Follow these steps to integrate the Modusign MCP Server with Cursor.

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using Modusign

Open Agent mode in chat and ask: "Using Modusign, help me...". 10 tools available

Why Use Cursor with the Modusign MCP Server

Cursor AI Code Editor provides unique advantages when paired with Modusign through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Modusign + Cursor Use Cases

Practical scenarios where Cursor combined with the Modusign MCP Server delivers measurable value.

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Modusign MCP Tools for Cursor (10)

These 10 tools become available when you connect Modusign to Cursor via MCP:

create_document_from_template

Create document from template

get_audit_logs

Get document audit logs

get_document

Get specific document details

get_org_info

Get organization metadata

list_automations

List signature automations

list_documents

List electronic documents

list_external_files

List external document files

list_folders

List document folders

list_templates

List contract templates

list_webhooks

List active webhooks

Example Prompts for Modusign in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with Modusign immediately.

"List my most recent electronic documents."

"Send a 'Standard NDA' to ryan@example.com using template ID tmp_123."

"Show me the audit logs for document doc_987."

Troubleshooting Modusign MCP Server with Cursor

Common issues when connecting Modusign to Cursor through the Vinkius, and how to resolve them.

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Modusign + Cursor FAQ

Common questions about integrating Modusign MCP Server with Cursor.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.