dokutrak-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOKUTRAK_API_KEY | Yes | The Agent Connection, from Settings → Connect an agent. | |
| DOKUTRAK_API_URL | No | Base URL of the API. Ends in /api; the connector adds /v1. | https://app.dokutrak.com/api |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_requestA | Call this when the Professional wants to ask a Client for documents: it creates the Document Request and sends the email in one step, so nothing is left created but unsent. Provide the Client email, a deadline, and the list of documents wanted, plus an optional title and a message written by the Professional. The email goes to the recipient given here and to nobody else, and the Client uploads through the secure link it contains. If the email fails after creation, the error names the created request so it can be sent from the dashboard. |
| request_replacementA | Call this when a Document Request has rejected files and the Professional wants the Client to send them again. It flags every rejected file, moves the request back to awaiting the Client, and returns it to the automatic reminder cadence, which is what reaches the Client. Nothing is emailed by this call itself, and the optional message is kept in the audit trail rather than sent. Do not use it on a request with no rejected file; get_request shows which files were rejected. |
| get_requestA | Call this when the Professional asks where a Document Request stands: which documents arrived, which were approved or rejected, and when the Client was last chased. Give the request id when you have it, or a search term matching the title, the Client name or the Client email; several matches come back as a short list to choose from. One call returns the status, the checklist, every collected file with its verdict, and the reminder state, so no follow-up read is needed. Approving or rejecting a document is the decision of the Professional, made in the DokuTrak dashboard, and no tool here can take it. |
| download_documentsA | Call this when the Professional wants the files a Client has uploaded on a Document Request, for example to file them or read them locally. It returns every collected document as one zip archive, embedded in the result as binary content. The archive is the same download the dashboard offers and comes back only to the agent of the Professional, never to a third party. Use get_request first to check that documents have actually arrived. |
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 4 tools
Each tool maps to a distinct action: create a new request, request replacement of rejected files, read request status, or download collected documents. The descriptions clearly state when not to use a tool, so there is little risk of selecting the wrong one.
All tools follow a consistent imperative verb_noun pattern: create_request, request_replacement, get_request, download_documents. The names clearly signal the action and object, and the pattern is maintained throughout the small set.
Four tools is well-scoped for the focused document-request workflow; each tool covers a necessary step: create, monitor, re-request, and download. There is no redundancy or overlap, so the small count feels deliberate rather than thin.
The core flow of requesting documents, checking status, re-requesting rejected files, and downloading is covered, but there is no general update or cancel/delete tool for a request. A Professional cannot adjust a deadline, change the document list, or withdraw a request through the MCP, which leaves a notable lifecycle gap.