Skip to main content
Glama

Labradoc MCP Server

A Model Context Protocol (MCP) server that exposes Labradoc API capabilities as MCP tools. This enables AI assistants like Claude Desktop, OpenAI Agents, and other MCP-compatible clients to interact with Labradoc's document management, email ingestion, task extraction, and integration features.

Features

  • Files: List, search, get, and archive documents

  • Email: Manage inbound email addresses and view ingested emails

  • Tasks: List and close tasks extracted from documents

  • User: View usage statistics and purchase AI credits

  • Integrations: Connect Google Drive, Gmail, and Microsoft Outlook

Related MCP server: Document Tools

Requirements

  • Node.js 20+

  • A Labradoc API key

Quick Start

npx @labradoc/mcp

Or install globally:

npm install -g @labradoc/mcp
LABRADOC_API_KEY=your-key labradoc-mcp

Configuration

Variable

Required

Default

Description

LABRADOC_API_KEY

Yes

-

Your Labradoc API key

LABRADOC_API_URL

No

https://labradoc.eu

Labradoc API base URL

LABRADOC_LOG_LEVEL

No

info

Log level: debug, info, warn, error

Available MCP Tools

Files

Tool

Description

files_list

List user's files with optional status filter, pagination, and search

files_search

Search files by query string

files_get

Get a single file by ID

files_delete

Archive files by their IDs

Email

Tool

Description

email_addresses_list

List user's inbound email addresses

email_addresses_create

Request a new inbound email address

emails_list

List ingested emails

Tasks

Tool

Description

tasks_list

List tasks extracted from documents

tasks_close

Close/complete tasks by their IDs

User & Billing

Tool

Description

user_stats

Get user statistics (completed pages, unlimited pages status)

billing_checkout

Create a Stripe checkout session for AI credits

Integrations

Tool

Description

google_drive_status

Check if Google Drive is connected

google_drive_connect

Start Google Drive OAuth flow

google_gmail_status

Check if Gmail is connected

google_gmail_connect

Start Gmail OAuth flow

microsoft_outlook_status

Check if Microsoft Outlook is connected

microsoft_outlook_connect

Start Microsoft Outlook OAuth flow

Usage

Claude Desktop (macOS/Windows)

Edit your Claude Desktop configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "labradoc": {
      "command": "npx",
      "args": ["@labradoc/mcp"]
    }
  }
}

Or with a global install:

{
  "mcpServers": {
    "labradoc": {
      "command": "labradoc-mcp"
    }
  }
}

Set the API key in your environment or .env file:

LABRADOC_API_KEY=your-api-key

Claude CLI

claude mcp add labradoc -- npx @labradoc/mcp

Direct stdio Usage

LABRADOC_API_KEY=your-key npx @labradoc/mcp

Development

npm install
npm run build
LABRADOC_API_KEY=your-key node dist/index.js

License

MIT

Available Tools

17 tools
billing_checkoutB

Create a Stripe checkout session for AI credits

Inputs: no named parameters.

email_addresses_createB

Request a new inbound email address

Inputs: description.

email_addresses_listB

List user's inbound email addresses

Inputs: no named parameters.

emails_listB

List ingested emails

Inputs: no named parameters.

files_deleteC

Archive files by their IDs

Inputs: ids (required).

files_getA

Get a single file by ID

Inputs: file_id (required).

files_listC

List user's files with optional status filter, pagination, and search

Inputs: status, page_size, page_number, query.

google_drive_connectA

Start Google Drive OAuth flow to connect your account

Inputs: no named parameters.

google_drive_statusA

Check if Google Drive is connected

Inputs: no named parameters.

google_gmail_connectA

Start Gmail OAuth flow to connect your account

Inputs: no named parameters.

google_gmail_statusC

Check if Gmail is connected

Inputs: no named parameters.

microsoft_outlook_connectB

Start Microsoft Outlook OAuth flow to connect your account

Inputs: no named parameters.

microsoft_outlook_statusA

Check if Microsoft Outlook is connected

Inputs: no named parameters.

tasks_closeB

Close/complete tasks by their IDs

Inputs: ids (required).

tasks_listB

List tasks extracted from documents

Inputs: no named parameters.

user_statsA

Get user statistics including completed pages and unlimited pages status

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 17 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers