How to Use the Clustdoc MCP in VS Code Copilot

Q: How do I debug Clustdoc webhook payloads using VS Code Copilot?

Ask Copilot to run getapplicationstatusdetails. It pulls the current state of a dossier so you can compare it against your local webhook logs.

Q: Can I manage Clustdoc team assignments from VS Code Copilot?

Yes, you can. The agent uses listclustdocteams to retrieve team rosters, making it easy to check which developers or agents are assigned to specific dossiers.

Run Clustdoc workflows and audit team dossiers directly from your VS Code Copilot workspace.

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 team dossiers inside VS Code Copilot

The `list_client_dossiers` tool exposes active application tracking directly to your VS Code Copilot environment. Your engineering team can audit pipeline blockers without leaving the editor. Having this MCP Server active means your team can run `get_application_status_details` to debug integration issues. You can see exactly which step a client is stuck on when testing webhooks.

Trigger onboarding workflows from the editor

Use `launch_new_onboarding` to spin up test dossiers during local development. You do not need to manually click through the admin portal to generate test events. The `launch_new_onboarding` tool on this MCP Server lets you call `send_onboarding_invitation` to verify that your automated email triggers are firing correctly. Copilot handles the execution and displays the response payload inline.

Inspect workflow templates inline

The `list_onboarding_templates` tool fetches your production workflow structures directly into your workspace. This helps developers verify template configurations against local code updates. By running `get_workflow_configuration`, Copilot retrieves the exact requirements for any onboarding setup. You can write migration scripts or API mappings with confidence.

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-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

Yes, you can. By committing the MCP configuration file to your repository, every developer on your team gets immediate access to the tools.

Ask Copilot to run `get_application_status_details`. It pulls the current state of a dossier so you can compare it against your local webhook logs.

Yes, you can. The agent uses `list_clustdoc_teams` to retrieve team rosters, making it easy to check which developers or agents are assigned to specific dossiers.

No, you don't. The connection relies on a single secure token configured through your shared environment settings, keeping your credentials centralized.

All dossier metadata and client contact details are transmitted over encrypted TLS channels. The host platform runs an isolated sandbox that never writes this data to disk, ensuring strict compliance with your data privacy standards.

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