Bring Digital Signature
to VS Code Copilot
Learn how to connect Autenti to VS Code Copilot and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Autenti MCP Server?
Connect your Autenti account to any AI agent and take full control of your professional document signing workflows and e-signature compliance through natural conversation.
What you can do
- Process Orchestration — List and manage document signature processes programmatically, retrieving detailed status, high-fidelity metadata, and historical audit data in real-time
- Dynamic Lifecycle Management — Discover and execute available actions (Send, Sign, Reject) based on the document's current state to coordinate complex signature workflows
- Participant Intelligence — Programmatically add signers and observers to your processes and manage your organizational contact directory to ensure perfectly coordinated collaboration
- Event Monitoring — Access and monitor your complete directory of webhooks to receive real-time notifications for incoming document events directly through your agent
- Operational Visibility — Access high-fidelity profile metadata for your authenticated user and verify API connectivity directly through your agent for instant reporting
How it works
1. Subscribe to this server
2. Retrieve your OAuth Access Token from the Autenti Developer Portal
3. Start managing your digital trust pipeline from Claude, Cursor, or any MCP client
No more manual status checking of individual contracts or digging through fragmented email threads. Your AI acts as your dedicated digital signature coordinator and compliance architect.
Who is this for?
- Legal & Compliance Teams — instantly retrieve process statuses and execute signature actions using natural language commands
- Sales Professionals — automate the dispatch of agreements and monitor signer progress without leaving your creative workspace
- HR Managers — orchestrate employment contract workflows and manage participant directories through simple AI queries
Built-in capabilities (12)
Add a contact to your address book
Verify Autenti API connectivity
Requires a title and metadata. Start a new document process
Use list_available_process_actions first to find valid names. Execute a discovered action (e.g., Send, Sign, Reject)
Get details for a specific signature process
Get authenticated user profile
Discover possible actions for a process
List active webhooks
List files within a process
List signers and observers
List your address book contacts
List all document signature processes
Why VS Code Copilot?
GitHub Copilot Agent mode brings Autenti data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 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
Autenti in VS Code Copilot
Autenti and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Autenti 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 Autenti in VS Code Copilot
The Autenti 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 12 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
Autenti for VS Code Copilot
Every tool call from VS Code Copilot to the Autenti 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 Autenti Access Token?
Log in to the Autenti Developer Portal, navigate to your application settings, and generate an OAuth 2.0 Access Token.
Can I discover valid actions via AI?
Yes! The list_available_process_actions tool retrieves a dynamic list of valid operations (like SEND or SIGN) based on the document's high-fidelity status.
How do I add a new contact programmatically?
Use the add_new_contact tool to register a name and email in your Autenti address book for future high-fidelity signature requests.
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.