mcp-Docuplete
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCUPLETE_API_KEY | Yes | Your Docuplete API key. Get it from https://docuplete.com/settings/api-keys |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-packagesA | List all document packages configured on the Docuplete account. Returns package IDs, names, and descriptions. Use this first to discover available packages before creating a session. |
| get-packageA | Get full details for a specific document package, including its fields and documents. |
| create-sessionA | Start a new interview session for a document package. Returns the session token and a ready-to-use interview URL that can be sent to a recipient to complete the form. |
| get-sessionA | Check the current status and details of a session by its token. Status is one of: 'draft' (not started), 'in_progress' (form open), or 'generated' (PDF ready). Poll this tool to check for completion. |
| generate-pdfA | Finalise a session and trigger PDF generation. Returns a download URL for the completed PDF packet. Call this once the session status is 'in_progress' or after filling answers programmatically. |
| list-sessionsA | List recent sessions on the account with optional filters for package and status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct resource and action: packages have list/get, sessions have create/get/list, and PDF generation is separate. No ambiguity between tools.
All tool names follow a consistent verb-noun hyphenated pattern (list-, get-, create-, generate-), making the set predictable and easy to navigate.
With 6 tools, the set is well-scoped for managing document packages and sessions, covering discovery, creation, status tracking, and PDF generation without bloat.
The core workflow is fully covered: discover packages, create a session, monitor status, and generate the final PDF. No obvious gaps in the primary lifecycle.