Bring Client Onboarding
to VS Code Copilot
Learn how to connect Clustdoc to VS Code Copilot and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Clustdoc MCP Server?
Connect your Clustdoc account to any AI agent and take full control of your professional client onboarding and automated document collection workflows through natural conversation.
What you can do
- Application Orchestration — List and manage all active client applications programmatically, including monitoring completion percentages and real-time status changes
- Document Architecture — Organize and track the collection of critical business documents (KYC, contracts, IDs) by initializing high-fidelity application folders directly from your agent
- Workflow Intelligence — Access your directory of onboarding processes (templates) to ensure every new client follows the perfect perfectly coordinated legal and operational path
- Team Coordination — Retrieve directories of organization users and monitor team activities to oversee high-volume onboarding pipelines efficiently
- Operational Monitoring — Check active webhooks and retrieve specific application metadata directly through your agent for instant auditing and reporting
How it works
1. Subscribe to this server
2. Retrieve your API Token (Bearer) from your Clustdoc dashboard (Settings > API)
3. Start managing your client pipeline from Claude, Cursor, or any MCP client
No more manual following up on missing files or digging through student/client folders in the portal. Your AI acts as your dedicated onboarding specialist and document coordinator.
Who is this for?
- Account Managers & Legal Teams — instantly retrieve application summaries and check document completion using natural language commands
- Operations Specialists — automate the creation of new client files and track progress without leaving your communication tools
- Real Estate & HR Leads — monitor incoming tenant or employee applications and retrieve finalized PDFs through simple AI queries
Built-in capabilities (6)
Pass data as a JSON string. Create a new application
Get specific application details
List all client applications
List all team members
List all configured webhooks
List all onboarding workflow processes
Why VS Code Copilot?
GitHub Copilot Agent mode brings Clustdoc data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 6 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
Clustdoc in VS Code Copilot
Clustdoc and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Clustdoc 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 Clustdoc in VS Code Copilot
The Clustdoc 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 6 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
Clustdoc for VS Code Copilot
Every tool call from VS Code Copilot to the Clustdoc 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 Clustdoc API Token?
Log in to your account, navigate to Settings > API, and generate or copy your unique Bearer Token.
Can I start a specific onboarding process via AI?
Yes! The create_application tool allows you to specify a process_id to trigger the exact workflow template you need.
How do I check document completion status?
Use the get_application_details tool with an application ID to retrieve high-fidelity metadata including the current step and completion progress.
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.