# Clustdoc MCP MCP

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

## Overview
- **Category:** productivity
- **Price:** Free
- **Tags:** client-onboarding, document-collection, intake-workflows, application-tracking, secure-file-sharing, automation

## Description

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.

## Tools

### 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_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.

## Prompt Examples

**Prompt:** 
```
List all my active client applications in Clustdoc.
```

**Response:** 
```
I've retrieved your applications. You currently have 5 active submissions, including 'Alice Brown' (75% complete) and 'TechCorp KYC'. Which one would you like the full step-by-step progress for?
```

**Prompt:** 
```
Create a new onboarding file for 'John Doe' using the 'KYC' process.
```

**Response:** 
```
Application created! John Doe has been successfully initialized in your Clustdoc workspace using the KYC template. You can share his personal portal link to begin document collection: [portal_url].
```

**Prompt:** 
```
Show me the list of all onboarding team members.
```

**Response:** 
```
I've retrieved your team directory. You currently have 3 active members overseeing applications: @admin, @sarah, and @mike. Shall I check who is assigned to your most recent submission?
```

## Capabilities

### Track all active applications
List and get specific details for every client application in the system.

### Manage workflow templates
Browse your directory of available onboarding processes to see what steps are required for a given client type.

### Create new client files
Initialize an entire client application file using specific process templates and pass necessary starting data.

### Monitor team assignments
Retrieve a directory of users to see who is assigned to which applications or who works for the company.

### Audit system connections
List and check active webhooks to confirm which external systems are triggered by application changes.

## Use Cases

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

## Benefits

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

## How It Works

The bottom line is you use natural language to manage complex backend processes that used to require manual navigation through multiple dashboards.

1. Subscribe to the MCP and retrieve your API Token from your Clustdoc dashboard.
2. Connect your AI client (Claude, Cursor, etc.) using the token credentials.
3. Ask your agent a question like, 'What is the status of John Doe's application?' and get an instant report.

## Frequently Asked Questions

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