Labradoc MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LABRADOC_API_KEY | Yes | Your Labradoc API key | |
| LABRADOC_API_URL | No | Labradoc API base URL | https://labradoc.eu |
| LABRADOC_LOG_LEVEL | No | Log level: debug, info, warn, error | info |
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 |
|---|---|
| files_listC | List user's files with optional status filter, pagination, and search |
| files_searchB | Search files by query string |
| files_getA | Get a single file by ID |
| files_deleteC | Archive files by their IDs |
| email_addresses_listB | List user's inbound email addresses |
| email_addresses_createB | Request a new inbound email address |
| emails_listB | List ingested emails |
| tasks_listB | List tasks extracted from documents |
| tasks_closeB | Close/complete tasks by their IDs |
| user_statsA | Get user statistics including completed pages and unlimited pages status |
| billing_checkoutB | Create a Stripe checkout session for AI credits |
| google_drive_statusA | Check if Google Drive is connected |
| google_drive_connectA | Start Google Drive OAuth flow to connect your account |
| google_gmail_statusC | Check if Gmail is connected |
| google_gmail_connectA | Start Gmail OAuth flow to connect your account |
| microsoft_outlook_statusA | Check if Microsoft Outlook is connected |
| microsoft_outlook_connectB | Start Microsoft Outlook OAuth flow to connect your account |
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 17 tools
Each tool targets a distinct resource or action: billing, email addresses, ingested emails, files, cloud service connections (Drive, Gmail, Outlook), tasks, and user stats. Descriptions clearly differentiate overlapping areas like email addresses vs ingested emails vs Gmail status.
Most tools follow a consistent verb_noun pattern in snake_case (e.g., files_list, google_drive_connect). Minor deviations exist: 'billing_checkout' uses a non-standard verb, and 'user_stats' abbreviates. Overall pattern is clear and predictable.
17 tools cover a broad domain including files, email, cloud integrations, tasks, and billing. The count is slightly above the typical 3-15 range but each tool serves a distinct purpose, making the set well-scoped without bloat.
Notable gaps exist: no file create/update, no task creation, no billing history or status, no ability to disconnect cloud services. While core retrieval and listing are covered, essential lifecycle operations are missing, which will hinder agent workflows.