How to Use the Clustdoc MCP in Cursor

Q: Can Cursor automatically write tests for my Clustdoc integrations?

Yes, it can. The MCP tool pulls real payload formats using getapplicationstatusdetails and writes precise unit tests based on your actual dossier structures.

Q: How do I reference Clustdoc template IDs while writing code in Cursor?

Ask the agent to run listonboardingtemplates. It fetches the active list directly into your chat, so you can copy the correct IDs straight into your environment files.

Q: Can I check my Clustdoc team permissions inside Cursor?

Yes, you can. The agent uses listclustdocteams to verify who has access to specific workflows, helping you debug permission logic during development.

Generate code and manage Clustdoc onboarding dossiers directly within the Cursor editor.

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 Cursor

Create your Vinkius account to connect Clustdoc to Cursor 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 Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build integrations with real Clustdoc data

The `list_client_dossiers` tool lets your agent fetch actual live dossiers directly into your Cursor workspace. You can write your custom webhook handlers using real payload structures instead of guessing with mock data. This MCP Server feeds live JSON structures to the editor. You get accurate auto-completions based on the actual fields returned by your active onboarding pipelines.

Test onboarding triggers in Cursor

Use `launch_new_onboarding` to trigger fresh client files right from your editor's terminal or chat pane. You can test how your backend responds to new dossiers without leaving your code. Follow up by calling `send_onboarding_invitation` to verify the email delivery chain. Your agent runs these tests inline, saving you from constant browser switching.

Map templates to your local codebase

The `list_onboarding_templates` tool retrieves your active workflow configurations directly into Cursor via the MCP protocol. You can cross-reference your database schema with the actual steps defined in your portal. By calling `get_workflow_configuration`, your agent inspects the specific requirements of any flow. This lets you map out data syncs to your local database with perfect accuracy.

Setup guide

Set up Clustdoc MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Clustdoc MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Clustdoc transactions." If the MCP tools are loaded correctly, Cursor will call the Clustdoc tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/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 Cursor

Yes, it can. The MCP tool pulls real payload formats using `get_application_status_details` and writes precise unit tests based on your actual dossier structures.

Ask the agent to run `list_onboarding_templates`. It fetches the active list directly into your chat, so you can copy the correct IDs straight into your environment files.

Yes, you can. The agent uses `list_clustdoc_teams` to verify who has access to specific workflows, helping you debug permission logic during development.

No, you don't. You can connect to the hosted MCP endpoint by adding the URL to your local configuration file, letting your editor talk to the API immediately.

Your template schemas and workflow configurations are processed entirely in memory. The connection uses zero-trust architecture, meaning your proprietary onboarding steps are never cached or stored on external servers.

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