Bring Sproof
to VS Code Copilot
Learn how to connect Sproof to VS Code Copilot and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Sproof MCP Server?
Connect your Sproof account to any AI agent to automate your European-compliant digital signature workflows. Sproof provides a premier platform for qualified electronic signatures (QES), and this integration allows you to retrieve document metadata, monitor signature requests, and manage contacts through natural conversation.
What you can do
- Document Orchestration — List all managed documents and retrieve detailed profile metadata, including signature status programmatically.
- Signature Request Control — Create and monitor signature requests to ensure your legal documents are executed efficiently directly from the AI interface.
- Contact Management — Access and monitor your contact database to keep your signer records synchronized via natural language.
- Profile & Account Oversight — Retrieve detailed account profile metadata and monitor system usage to ensure your signature pipeline is optimized.
- Compliance Monitoring — Track document validity and signature authenticity using simple AI commands.
How it works
1. Subscribe to this server
2. Enter your Sproof API Key from your account settings
3. Start managing your digital signatures from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Legal & Compliance Officers — quickly retrieve document statuses and monitor signature requests without switching apps.
- HR Managers — automate the sending of employment contracts for signature via natural conversation.
- Administrative Leads — streamline the management of signed documents and monitor contact metadata directly within the chat.
Built-in capabilities (11)
Cancel a pending signature request
Create a new contact for signing
Pass data as a JSON string. Create a new signature request
Get document details
Get account profile details
Get details for a signature request
Get the audit trail for a signature request
List all contacts
List all documents
List all signature requests
List all signers for a signature request
Why VS Code Copilot?
GitHub Copilot Agent mode brings Sproof data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 11 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
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
Sproof in VS Code Copilot
Sproof and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Sproof to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Sproof in VS Code Copilot
The Sproof 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. All 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* 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
How Vinkius secures
Sproof for VS Code Copilot
Every tool call from VS Code Copilot to the Sproof MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Sproof API Key?
Log in to your Sproof account, navigate to Account Settings > API, and you will find your unique secret API Key there.
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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
