How to Use the Clustdoc MCP in VS Code Copilot

Q: How do we share the Clustdoc server setup with our team in VS Code Copilot?

Create a .vscode/mcp.json file in your repository root and commit it to Git. Every team member with VS Code Copilot will automatically gain access to the onboarding tools when they open the workspace.

Q: Can VS Code Copilot trigger new Clustdoc applications?

Yes, the agent can call createapplication using a JSON string parameter. You can ask Copilot Chat to run this tool during testing to verify that your document workflows trigger correctly.

Share Clustdoc onboarding workflows and application tracking across your team inside VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Clustdoc MCP to VS Code Copilot

Create your Vinkius account to connect Clustdoc to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Clustdoc with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Track Clustdoc files within VS Code Copilot

The `list_applications` tool feeds your active customer onboarding pipelines directly into your Copilot Chat sidebar. Your engineering team can inspect document completion rates without leaving their active workspace files. When debugging client portals, ask VS Code Copilot to run `get_application_details` to check why a specific file failed validation. The agent reads the error codes directly from the server response to suggest code fixes.

Map onboarding workflows using this MCP Server

The `list_workflows` tool allows your team to query active document collection templates directly in the editor. This MCP Server setup lets developers write automated scripts that match these template IDs with local database records. If you need to test document creation during development, Copilot executes `create_application` with test payloads. It verifies that your backend systems send correctly formatted strings to the onboarding API.

Audit team access and webhook endpoints

The `list_team_members` tool pulls your active operator directory into the chat window. Your team uses this to write automated routing logic that assigns incoming document packages to specific reviewers. You can also call `list_webhooks` to inspect where document events are being sent. VS Code Copilot reviews this list to ensure your staging and production environments do not have conflicting listeners.

Setup guide

Set up Clustdoc MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Clustdoc MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Clustdoc tools listed. Try asking: "List my recent Clustdoc transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "clustdoc-alternative-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Clustdoc. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Clustdoc now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Clustdoc MCP in VS Code Copilot

Create a `.vscode/mcp.json` file in your repository root and commit it to Git. Every team member with VS Code Copilot will automatically gain access to the onboarding tools when they open the workspace.

Yes, the agent can call `create_application` using a JSON string parameter. You can ask Copilot Chat to run this tool during testing to verify that your document workflows trigger correctly.

You need VS Code version 1.96 or higher with Copilot Chat enabled. Once your workspace configuration file is active, switch Copilot to Agent mode to allow tool execution.

No, the tools return metadata and application states, not raw file binaries. You use `get_application_details` to retrieve secure download links, which your agent can display in your chat.

All tool calls route through Vinkius's zero-trust V8 sandbox, which isolates your team rosters and client submission metadata. No onboarding data is stored locally or used to train the underlying models.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript