Bring Client Onboarding
to Cursor
Learn how to connect Clustdoc to Cursor 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 Cursor?
Cursor's Agent mode turns Clustdoc into an in-editor superpower. Ask Cursor to generate code using live data from Clustdoc and it fetches, processes, and writes. all in a single agentic loop. 6 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Clustdoc in Cursor
Clustdoc and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Clustdoc to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.