Clustdoc MCP for AI. Manage client intake from a single chat window.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Connect to your AI in seconds.
Clustdoc helps you manage entire client onboarding pipelines directly through conversation. Use this MCP to track application status, organize required documents like IDs and contracts, and automate the creation of new client files.
It gives your agent full visibility into complex intake workflows without needing to log into the portal.
What your AI can do
Create application
Initializes a brand new client file using predefined process templates.
Get application details
Pulls up the specific, granular details for any single client application record.
List applications
Retrieves a list of all active and completed applications in your system.
List and get specific details for every client application in the system.
Browse your directory of available onboarding processes to see what steps are required for a given client type.
Initialize an entire client application file using specific process templates and pass necessary starting data.
Retrieve a directory of users to see who is assigned to which applications or who works for the company.
List and check active webhooks to confirm which external systems are triggered by application changes.
Ask an AI about this
Waiting for input…
Clustdoc: 6 Tools for Application Ops
These tools let you manage the full lifecycle of client applications, from initializing a file to checking system integrations and team assignments.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Clustdoc on VinkiusCreate Application
Initializes a brand new client file using predefined process templates.
Get Application Details
Pulls up the specific, granular details for any single client application record.
List Applications
Retrieves a list of all active and completed applications in your system.
List Workflows
Displays your entire directory of available onboarding processes and templates.
List Team Members
Shows you the directory and names of all team members within the organization.
List Webhooks
Lists all configured webhooks that trigger external actions when an application status changes.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Claude AI
Open Claude Settings
Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.
Add Custom Connector
Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:
https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp
Replace [YOUR_TOKEN_HERE] with your token
from cloud.vinkius.com. For OAuth-protected servers, expand
Advanced settings to add credentials.
Start a conversation
Open a new chat. The Clustdoc integration is available immediately — no restart needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Clustdoc, then connect any of our 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 6 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The Pain Point: Manual Client Intake Management
Right now, managing a client's onboarding is a multi-tab nightmare. You open the portal to check status A; you switch to the CRM just to see who owns the file; then you have to jump into a separate sheet to track missing documents. Every time someone changes their name or moves departments, you’re copying data and updating five different places.
With this MCP, your agent acts like an internal expert who knows all the tabs and systems. You just talk to it. It accesses all active applications, tracks document progress against established workflows, and reports back on exactly what's missing—all without you ever leaving your chat window.
Clustdoc MCP: Getting Application Status & Document Control
You don't have to manually run reports or check every status field. You can ask the agent to `list_applications` and get a summary of all active submissions, including percentage completion for each one. Need deeper data? Just tell it to use `get_application_details` on a specific ID.
The difference is control. Instead of waiting for an Ops Specialist to run a report at the end of the day, you can query the system instantly and get structured metadata about any file or workflow in real time.
What your AI can actually do with this
When a client needs to onboard—whether they're signing a lease or applying for corporate KYC—the process is rarely simple. You need to track multiple documents, monitor progress against specific steps, and make sure every required form gets filled out correctly. This MCP lets your agent handle that complexity. Instead of manually following up on missing files or digging through separate folders in the client portal, you just ask your AI what's wrong with a submission.
It accesses all active applications, checks document completion percentages, and even shows you which team members are assigned to the file. If you need visibility into how the process works, this connection gives you access to your entire directory of onboarding templates, letting you understand exactly what steps follow next.
You connect it via Vinkius, giving any MCP-compatible client instant control over your entire client intake operation.
019dd0d2-ec2e-73ad-b19d-651ff4e17bee 
Here's how it actually works
The bottom line is you use natural language to manage complex backend processes that used to require manual navigation through multiple dashboards.
Subscribe to the MCP and retrieve your API Token from your Clustdoc dashboard.
Connect your AI client (Claude, Cursor, etc.) using the token credentials.
Ask your agent a question like, 'What is the status of John Doe's application?' and get an instant report.
Who is this actually for?
Account Managers and Operations Specialists who are tired of spending time cross-referencing status updates across separate portals. You're the person who needs a single source of truth for client onboarding progress.
You check if all required documents (KYC, IDs) have been submitted and need application summaries instantly.
You automate the creation of new client files and track progress without leaving your communication tool.
You audit active webhooks and check application metadata to ensure compliance records are logged correctly.
What Changes When You Connect
Instant visibility into client progress. Instead of clicking through multiple dashboards, you ask your agent to use list_applications and get an immediate count and status update for every active submission.
Build new client files instantly. You can tell your agent to create_application using a specific template (like KYC), initializing the file and sending the client their personal link immediately.
Keep track of the process itself. Use list_workflows to see all available onboarding templates, ensuring that every new hire or tenant follows the required legal path.
Streamline team oversight. Running list_team_members lets you check who's managing which files across your high-volume pipelines without leaving your communication tool.
Full audit control. Checking list_webhooks allows you to confirm that every status change triggers the necessary external system update, giving you instant reporting capability.
See it in action
The Missing Document Chase
A manager needs to know why a client file is stalled. Instead of emailing three people or checking five different dashboards, they ask their agent to use get_application_details. The agent reads the specific application metadata and reports: 'File is paused; awaiting signed ID from Legal.' The problem is solved in seconds.
Onboarding a New Client Type
The legal team needs to start onboarding a new corporate client. They first use list_workflows to find the correct 'Corporate KYC' process, then instruct their agent to create_application for the new company using that specific template.
Reviewing Team Capacity
The operations lead is worried about burnout. They run list_team_members and cross-reference it with the list of active applications to see who has taken on too many files, allowing them to reassign workload efficiently.
Validating System Integrations
Before a major launch, an engineer needs to confirm all external systems are hooked up. They use list_webhooks and check the status of each one, verifying that every single application stage triggers the correct API call.
The honest tradeoffs
Trying to track progress without knowing templates
Asking the agent simply to 'Check client Alpha's status.' The agent can't answer because it doesn't know which official process (workflow) Client Alpha is supposed to be using.
First, use list_workflows to identify the correct template for Client Alpha. Then, instruct your agent to create_application, pointing it to that specific workflow ID so the tracking starts correctly.
Assuming all applications are visible
Asking 'Show me all my clients.' This query is too vague and could pull unrelated data, leading to incomplete or massive results.
Always start by using list_applications to get a defined list of active submissions. If you need deep detail on one specific submission, then use get_application_details with the ID provided by the list.
Handling multiple data types manually
Creating an application, then separately checking team capacity, and finally reviewing webhooks. This requires three separate prompts and context switching.
Group your requests. Ask the agent to 'Create a new application for Jane Doe using the HR onboarding process, and also tell me who is currently assigned to her file.' This handles multiple steps in one go.
When It Fits, When It Doesn't
Use this MCP if your primary problem is managing the state and lifecycle of structured client intake data. If you need to create a record using defined rules (workflows) or audit who has access, this is what you need. Don't use it if your goal is just simple messaging—don't expect it to send a 'Hi!' message. For general communication logs or chat history retrieval, look for a dedicated messaging MCP. Also, if you only need to check the list of users and nothing else, using list_team_members in isolation might be enough; but when you pair that with create_application, this MCP provides the full context.
Questions you might have
How do I use the list_applications tool with Clustdoc MCP? +
You simply ask your agent to 'List all active client applications.' It pulls a comprehensive roster, showing you key identifiers and current completion percentages for every submission.
Can I create an application using the list_workflows tool? +
No. Use list_workflows only to view your available templates first. After reviewing the options, then use create_application and reference the specific workflow ID you want to start with.
Does get_application_details show me everything about a client? +
It shows granular metadata for one application only. If you need an overview of many clients, run list_applications first; then drill down using get_application_details.
What is the purpose of list_webhooks in this MCP? +
list_webhooks shows you every automated connection. You check it to ensure that when an application status changes, the necessary external systems—like your billing platform—are actually getting triggered.
How do I handle authentication when running the list_team_members tool? +
Your AI client uses a Bearer API Token for secure access. You retrieve this token from your Clustdoc dashboard settings and pass it to Vinkius. The MCP manages passing this credential, so you don't have to worry about handling it manually in the prompts.
What happens if I try to create an application using the create_application tool with incomplete data? +
The system won't just fail; it returns a structured JSON error message. This message points out exactly which required field is missing or formatted incorrectly, making debugging simple for your agent.
Are there rate limits if I call the list_applications tool frequently? +
Yes, like all APIs, there are usage limits to prevent abuse. If you hit a limit by calling list_applications too often in a short period, the API will return an HTTP 429 error code. It's best practice to include backoff logic in your agent.
What kind of information do I get when I call the list_workflows tool? +
The tool provides a catalog of all available onboarding process templates. You receive the workflow name, a description of its function, and details on any initial parameters required to launch that specific process.
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.
We've already built the connector for Clustdoc. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 6 tools are live and waiting.
You're up and running in seconds.
Gemini Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.