Can I send documents for signature?

Yes! Use `send_envelope` with a JSON payload defining the documents, recipients, and signature tabs.

How do I check who signed?

Use `list_recipients` with the envelope ID to see all signers and their status.

Can I cancel a pending signature request?

Yes! Use `void_envelope` with the envelope ID and a reason. This is irreversible.

DocuSign MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: DocuSign
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 DocuSign and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "docusign": {
      "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 DocuSign MCP Server

Connect DocuSign to any AI agent and automate your entire contract lifecycle.

GitHub Copilot Agent mode brings DocuSign 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

Envelope Management — List, view, search, and send envelopes for signature
Template Library — Browse and use pre-built templates for recurring documents
Recipient Tracking — Check who has signed and who hasn't
Signing URLs — Generate embedded signing links for instant signing
Void Envelopes — Cancel pending signature requests
Folder Organization — Browse envelope folders

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

Follow these steps to integrate the DocuSign 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 DocuSign

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

Why Use VS Code Copilot with the DocuSign MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with DocuSign 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

DocuSign + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the DocuSign 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

DocuSign MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect DocuSign to VS Code Copilot via MCP:

get_envelope

Get envelope details

get_signing_url

Provide envelope ID and recipient details as JSON. Generate a signing URL for a recipient

get_template

Get template details

list_envelopes

Provide a from_date in ISO format. List envelopes (documents sent for signature)

list_folders

List envelope folders

list_recipients

List recipients of an envelope

list_templates

List available envelope templates

search_envelopes

Search envelopes by text

send_envelope

Provide envelope definition as JSON. Create and send a new envelope for signature

void_envelope

Requires a reason. This action is irreversible. Void a sent envelope

Example Prompts for DocuSign in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with DocuSign immediately.

"Show me all envelopes from the last 30 days."

"Generate a signing link for the pending contract."

"List all available templates."

Troubleshooting DocuSign MCP Server with VS Code Copilot

Common issues when connecting DocuSign 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.

DocuSign + VS Code Copilot FAQ

Common questions about integrating DocuSign 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.