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 VS Code Copilot 10 tools — connect in under 2 minutes

Name: Modusign
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

GitHub Copilot Agent mode brings Modusign data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Modusign MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Modusign

Ask Copilot: "Using Modusign, help me...". 10 tools available

Why Use VS Code Copilot with the Modusign MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Modusign through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Modusign + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Modusign MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Modusign MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Modusign to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting Modusign to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Modusign + VS Code Copilot FAQ

Common questions about integrating Modusign MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.