How do I get a Docupilot API Key?

Log in to your Docupilot account, navigate to **Settings > API Key**, and you can generate or retrieve your unique API Key from there.

Can the agent show me the merge fields for a template?

Yes, you can use the get_template_merge_field_audit tool to retrieve exactly which data keys are needed to populate a specific template.

What formats does Docupilot support for output?

Docupilot supports generating documents in PDF, Microsoft Word (.docx), and other popular formats depending on your template type.

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

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

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "docupilot": {
      "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 Docupilot MCP Server

Integrate Docupilot, the powerful document automation platform, directly into your AI workflow. Manage your dynamic document templates, trigger high-volume document merges from JSON data, monitor generation status, and access output files using natural language.

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

Template Oversight — List and retrieve detailed configuration and field schemas for all your document templates.
Document Merging — Trigger the Docupilot engine to create new files by merging provided data into your professional templates.
Generation Tracking — Monitor the status of your document merges and access secure download URLs for output files.
Field Intelligence — Identify exactly which merge fields are required to populate specific templates accurately.

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

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

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

Why Use VS Code Copilot with the Docupilot MCP Server

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

Docupilot + VS Code Copilot Use Cases

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

Docupilot MCP Tools for VS Code Copilot (10)

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

get_document_generation_status

Get the current status and output URL for a specific generated document

get_docupilot_account_metadata

Retrieve metadata and usage limits for your Docupilot account

get_template_merge_field_audit

Identify exactly which merge fields are required to populate a template

get_template_schema

Get detailed information and field schema for a specific template

list_docupilot_templates

List all document templates available in your Docupilot account

list_failed_document_merges

Identify document merges that failed due to data or template errors (mock logic)

list_generated_documents

List all documents that have been generated/merged in Docupilot

list_latest_document_merges

Identify the most recently merged documents

search_docupilot_templates

Search for a document template using a name keyword

trigger_document_merge

Create a new document by merging data into a specific template

Example Prompts for Docupilot in VS Code Copilot

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

"List all available Docupilot templates."

"Generate an 'Employee Offer Letter' with data: {'name': 'Robert Brown', 'role': 'Engineer', 'salary': '90k'}."

"Show me the status of document 'DOCU-MERGE-12345'."

Troubleshooting Docupilot MCP Server with VS Code Copilot

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

Docupilot + VS Code Copilot FAQ

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