Log inSubmit server
Clio MCP logo

Clio MCP

Connect Claude to Clio for matters, contacts, documents, tasks, calendars, and billing workflows.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Clio MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "clio-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "@oktopeak/clio-mcp"
      ],
      "env": {
        "READ_ONLY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y @oktopeak/clio-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked Today.

Overview

The clio-mcp MCP server connects Claude to Clio through tools for matters, contacts, documents, folders, tasks, calendars, and billing data. It uses Clio OAuth 2.0, runs locally by default, and provides both read and write operations through standard MCP transports. Use it when an agent needs live Clio data or controlled updates without moving practice-management records into a separate system.

Use cases

  • Search matters and contacts from Claude
  • Create and update Clio matters
  • Upload documents to matters
  • Create tasks and calendar entries
  • Log billable time and expenses

Key features

  • Clio OAuth 2.0 authentication
  • Matter and contact management
  • Document and folder search
  • Task and calendar operations
  • Billing activity and time tracking
  • Optional read-only mode

Tools37

What Clio MCP lets your agent do. Expand a tool for its parameters.

Self-reported~1.2k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · @oktopeak/clio-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars25Stargazers on the source repository.
npm downloads924Package downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.
Tools exposed37Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Clio MCP works

What clio-mcp MCP server does

The clio-mcp MCP server gives Claude access to Clio practice-management data through MCP tools. It covers matter records, contacts, matter relationships, custom fields, documents, folders, tasks, calendars, time entries, expenses, and other Clio activities.

Read operations include searching contacts, listing and inspecting matters, finding documents or folders by query, reviewing tasks and calendar entries, and retrieving billable time or expense records. Write operations can create or update matters, custom fields, tasks, calendar entries, folders, time entries, and activities. Documents can be uploaded to a matter, while document metadata and download URLs can be retrieved.

This places the connector in the ⚖️ Legal category and makes it relevant for firms using Clio as their primary practice-management system. Agents can work with live records instead of relying on manually exported context.

How it works

Authentication uses Clio’s OAuth 2.0 browser flow. The authenticate tool opens Clio’s login page, and the connector does not handle the user’s Clio password. Authentication status and logout are available through separate tools.

The default architecture is local: the connector runs on the user’s machine and sends API traffic directly to Clio. OAuth access and refresh tokens are encrypted at rest with AES-256-GCM; the encryption key is held in the operating system keychain. Tool calls are recorded in a local audit log at ~/.clio-mcp/audit.log.

Many list operations return pagination metadata, including total_count, has_more, and next_page_token. Agents should pass the next-page token back when they need complete results. Before using custom fields, the documentation recommends listing their definitions. Matter stages should likewise be listed before assigning a matter_stage_id.

Setup and configuration

The clio-mcp MCP server is intended to use a developer-registered Clio application in its default local setup. After installation, authenticate with the auth command or the authentication tool, then configure the MCP client to launch the server.

The package also provides an account export command that writes Clio data to a selected local folder in read-only form. Run authentication first when using that command.

A READ_ONLY=true configuration removes write tools from the server. This is useful for evaluating access before enabling operations that change Clio records.

Tools and capabilities

  • Authenticate, inspect session status, or clear local credentials.
  • List, inspect, create, and update matters, including custom field values.
  • Discover custom field definitions and matter stages.
  • Search contacts and inspect their details and matter relationships.
  • List, search, download, upload, and organize documents and folders.
  • Create, update, list, and complete tasks.
  • Read available calendars and create or list calendar entries.
  • Review or record time entries, expenses, and other Clio activities.

Limitations and notes

The connector does not delete Clio records. Write access is optional and can be disabled with read-only mode. Folder creation should be preceded by an exact-name existence check to reduce duplicate folders. Document and folder searches require at least one relevant scope such as a matter ID, parent ID, or search query.

The audit log is append-only and remains on the local machine; older releases may have recorded more sensitive query content, so installations upgraded from earlier versions should review the existing log.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Clio MCP

clio-mcp is an MCP server that connects Claude to Clio practice-management data. Its main tools cover matters, contacts, documents, folders, tasks, calendars, time entries, expenses, and authentication. It runs locally by default, uses Clio OAuth 2.0, and can read records or perform configured write operations.

Install the `@oktopeak/clio-mcp` npm package and configure your MCP client to launch it. The default setup uses your own Clio developer application, after which you authenticate through Clio’s browser-based OAuth flow.

Yes, set `READ_ONLY=true` to remove write tools from the server. This leaves the connector focused on reading Clio data and is suitable for an initial evaluation before allowing matter, task, calendar, document, or billing activity changes.

It authenticates through Clio’s OAuth 2.0 browser flow. The authentication tool opens Clio’s login page, while access and refresh tokens are encrypted locally; the connector does not store or handle the user’s Clio password.

Yes, supported list and search tools return pagination metadata such as `total_count`, `has_more`, and `next_page_token`. Pass the next-page token into a subsequent request when an agent needs more than the first page.

Related MCP servers

All in Legal All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewClio MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/clio-mcp-2?style=directory)](https://allmcps.com/mcp/clio-mcp-2)
HTML Embed
<a href="https://allmcps.com/mcp/clio-mcp-2"><img src="https://allmcps.com/api/badge/clio-mcp-2?style=directory" alt="Clio MCP on AllMCPs" /></a>