Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words
Beginner mode Off
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenuSettings
Beginner mode Off
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

Clio MCP

by oktopeakversion 2.5.0i★ –iRuns on your computer
Registry nameio.github.oktopeak/clio-mcp

Install

Overview

Description from the maker (original English)

Connect Claude to Clio (37 tools), and export a whole Clio account, documents included.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Docs, sheets & office work
  • You need to fill in: CLIO_CLIENT_ID, CLIO_CLIENT_SECRET, ENCRYPTION_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: CLIO_CLIENT_ID, CLIO_CLIENT_SECRET, ENCRYPTION_KEY, CLIO_REDIRECT_PORT, CLIO_REGION, READ_ONLY, CLIO_API_BASE, CLIO_AUTH_URL, CLIO_TOKEN_URL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "clio": {
      "command": "npx",
      "args": [
        "-y",
        "@oktopeak/clio-mcp"
      ],
      "env": {
        "CLIO_CLIENT_ID": "your-value",
        "CLIO_CLIENT_SECRET": "your-value",
        "ENCRYPTION_KEY": "your-value",
        "CLIO_REDIRECT_PORT": "your-value",
        "CLIO_REGION": "your-value",
        "READ_ONLY": "your-value",
        "CLIO_API_BASE": "your-value",
        "CLIO_AUTH_URL": "your-value",
        "CLIO_TOKEN_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add clio --env CLIO_CLIENT_ID=your-value --env CLIO_CLIENT_SECRET=your-value --env ENCRYPTION_KEY=your-value --env CLIO_REDIRECT_PORT=your-value --env CLIO_REGION=your-value --env READ_ONLY=your-value --env CLIO_API_BASE=your-value --env CLIO_AUTH_URL=your-value --env CLIO_TOKEN_URL=your-value -- npx -y @oktopeak/clio-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "clio": {
      "command": "npx",
      "args": [
        "-y",
        "@oktopeak/clio-mcp"
      ],
      "env": {
        "CLIO_CLIENT_ID": "your-value",
        "CLIO_CLIENT_SECRET": "your-value",
        "ENCRYPTION_KEY": "your-value",
        "CLIO_REDIRECT_PORT": "your-value",
        "CLIO_REGION": "your-value",
        "READ_ONLY": "your-value",
        "CLIO_API_BASE": "your-value",
        "CLIO_AUTH_URL": "your-value",
        "CLIO_TOKEN_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "clio": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@oktopeak/clio-mcp"
      ],
      "env": {
        "CLIO_CLIENT_ID": "your-value",
        "CLIO_CLIENT_SECRET": "your-value",
        "ENCRYPTION_KEY": "your-value",
        "CLIO_REDIRECT_PORT": "your-value",
        "CLIO_REGION": "your-value",
        "READ_ONLY": "your-value",
        "CLIO_API_BASE": "your-value",
        "CLIO_AUTH_URL": "your-value",
        "CLIO_TOKEN_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • CLIO_CLIENT_ID required env
    Client ID from your Clio developer application (Settings → Developer Applications)
  • CLIO_CLIENT_SECRET secret required env
    Client Secret from your Clio developer application
  • ENCRYPTION_KEY secret env
    Optional. Leave unset to auto-generate a key stored in the OS keychain (or ~/.clio-mcp/key.hex as fallback on headless Linux/WSL2). If set, must be a 64-character hex string — it will be migrated to…
  • CLIO_REDIRECT_PORT env
    Local port for the OAuth callback listener (default: 5678). Change if 5678 is in use.
  • CLIO_REGION env
    Clio data region: 'us' (default, app.clio.com), 'eu' (eu.app.clio.com), 'au' (au.app.clio.com), or 'ca' (ca.app.clio.com). Controls the API and OAuth base URLs. Fixed at Clio account creation; must m…
  • READ_ONLY env
    Optional. 'true', '1' or 'yes' leaves the twelve write tools (create_matter, create_custom_field, create_note, create_task, update_task, complete_task, create_calendar_entry, log_time_entry, create_a…
  • CLIO_API_BASE env
    Advanced override for the Clio API base URL (e.g. https://eu.app.clio.com/api/v4). Takes precedence over CLIO_REGION.
  • CLIO_AUTH_URL env
    Override the OAuth authorization endpoint (e.g. https://eu.app.clio.com/oauth/authorize).
  • CLIO_TOKEN_URL env
    Override the OAuth token endpoint (e.g. https://eu.app.clio.com/oauth/token).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account oktopeak, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Docs, sheets & office worki

  • More stars than 0% of the other 3604 servers in this category
  • Published to the registry more recently than 84% of the other 3604 servers in this category
  • Basic checks equal to or better than 100% of the other 3604 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Clio MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: CLIO_CLIENT_ID, CLIO_CLIENT_SECRET, ENCRYPTION_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.5.0) reached the registry 5 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Calendar

Agent-Native Google Calendar - manage events, sync, and public booking

by BuilderIOWidely used★ 7.6KUpdated 2 months ago

Runs in the cloud
Install

Excel MCP Server

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

by haris-musaWidely used↓ 49.6K/wk★ 4.3KUpdated 8 days ago

Runs on your computer
Install

MCP Server for Excel

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

by sbroenneGrowing↓ 4.3K/wk★ 847Updated 6 days ago

Runs on your computer
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Clio MCP Server: Connect Claude to Clio Practice Management

### Built by Oktopeak: AI transformation & automation for law firms

Digital transformation for legal and healthcare businesses. We build AI integrations, workflow automation, and custom software your firm owns outright, including this connector. → Book a 30-min call

*Twenty-six seconds on what the connector does for a whole firm: runs in your own cloud, each person signs in with their own Clio login, one audit log, one automation built each month, $300 a month flat. Watch it.*

Open-source Model Context Protocol (MCP) connector that lets Claude read live data from Clio (matters, custom fields, notes, contacts, documents, folders, tasks, calendar, and billing) without copying client information into chat windows. Built for law firms that care about attorney-client privilege, ABA Opinion 512 compliance, and keeping AI workflows inside their existing practice management stack.

TL;DR: 37 Clio tools exposed to Claude across stdio and HTTP/SSE transports. Audit-logged for ABA Opinion 512. OAuth tokens encrypted at rest with AES-256-GCM. Local-only by default: you register your own Clio developer app, and no relay server sits in between. A separate one-click "listed" variant for the Clio App Directory uses a minimal login-only broker instead, see Listed / one-click install variant. MIT license, free forever.

Who this is for: Law firm IT, legal operations teams, tech-forward partners, and engineers at legal tech companies. If you can follow a five-step terminal install, you can use this.

[!TIP]

Not a developer? You don't need to be.

The README below assumes someone comfortable editing a JSON config file. If that's not you or your team, we deploy this for law firms: scoped credentials, audit log wired in, one custom workflow, training. A simpler one-command installer is also planned for v0.2.

→ Whole firm? The Firm Plan: $300 a month. Set up in your own cloud, every attorney signs in with their own login, one audit log, one automation built for you each month, no setup fee, cancel any time. → oktopeak.com/firm-plan/, or book a 30-min call

Jump to: Demo · Setup · Available tools · Export your whole account · Security & compliance · Need it deployed for you?

Demo

Watch Claude pull live data from Clio in under a minute (matters, contacts, tasks) without copying client information into chat.

▶ Watch the 60-second demo on YouTube

Setup tips + ABA Opinion 512 compliance updates for firms building with Claude + Clio.

→ Subscribe to Oktopeak Builder Notes. Short emails, easy unsubscribe.

New in 2.5.0: export your whole account

npx @oktopeak/clio-mcp export --out copies every matter, contact, note, task, calendar entry, time entry, expense, bill and document out of Clio onto your own computer, read-only, under your own Clio app. Run npx @oktopeak/clio-mcp auth first. See Exporting your whole account.

Only want the export, not the Claude connector? The same command ships on its own as @oktopeak/clio-export: npx @oktopeak/clio-export --out . Walkthrough: oktopeak.com/clio-export/.

Upgrading from 2.0.1

If you installed before September 2026 you are on 2.0.1, and there is one reason to upgrade that is worth stating plainly rather than burying in a changelog.

2.0.1 writes client data to its audit log. Contact search queries, note subjects, matter descriptions and custom field values were all recorded verbatim in ~/.clio-mcp/audit.log. The log is a plain file that nothing rotates. Since 2.2.0 audit entries carry ids, counts, dates and page tokens only, enforced by an allowlist rather than a denylist, with a test that fails if any tool ever starts logging content again.

npm install -g @oktopeak/clio-mcp@latest   # or just restart Claude Desktop if you use npx

Your existing ~/.clio-mcp/audit.log still contains whatever the old version put there. It is worth reading before you decide what to do with it.

Also new since 2.0.1: custom fields and notes on matters and contacts, folder tools, matter relationships, a one-call activity summary across open matters, a config-level READ_ONLY mode, and full pagination on reads where a short answer would be a wrong one. See CHANGELOG.md.

Compliance & Security

This section exists because law firms evaluating AI tools have asked the right questions. Here are direct answers.

ABA Formal Opinion 512: AI and competence

ABA Opinion 512 (2023) requires attorneys using AI tools to understand how those tools work, supervise their outputs, and maintain confidentiality of client information. This connector is designed with those obligations in mind:

  • Audit log. Every tool call (every time Claude queries Clio on your behalf) is appended to a local log file at ~/.clio-mcp/audit.log. Each entry records the timestamp, which tool was invoked, what arguments were passed, whether it succeeded, and the Clio user ID. The log is stored on your machine, not in any cloud service. It is append-only and never purged by the software, so your firm retains a complete record of AI-initiated data access.
  • No data retention by the connector. The connector itself does not store matter data, client names, or any Clio content. It fetches from the API and passes results to Claude. The only thing it persists locally is your authentication token, and that is encrypted (see below). The separate export command is the one exception, by design: it writes a local copy of your Clio data to the folder you choose, and nothing else does.
  • Twelve write tools, all logged, all optional. The connector can create matters, custom fields, notes, tasks, folders, calendar entries, time entries and activities, update matters and tasks, complete tasks, and upload documents. It never deletes anything and never touches contacts or billing records. Every write is recorded in the audit log, and READ_ONLY=true removes all twelve write tools from the server entirely (see Read-only mode), so a firm can start with read access and turn writes on when it has decided to.
Token security: encryption at rest

Your OAuth credentials are never stored in plain text. After you authenticate, the connector encrypts your access token and refresh token using AES-256-GCM, the same standard used by financial institutions, and writes the ciphertext to ~/.clio-mcp/tokens.enc. The encryption key is auto-generated on first run and stored in your OS keychain (macOS Keychain, Windows Credential Manager, or Linux Secret Service), never on the filesystem in plaintext.

If someone obtained the token file without the key, they would not be able to read it.

OAuth 2.0: no passwords stored

Authentication uses Clio's standard OAuth 2.0 flow. You log in through your browser on Clio's own login page. The connector never sees or handles your Clio password. CSRF protection is implemented via a cryptographic state parameter on every auth request.

Local-first architecture

The connector runs entirely on your machine. There is no Clio MCP cloud service, no relay server, no third party in the middle. Your Clio API traffic goes directly from your device to Clio's servers.

This is true for the default setup below, where you register your own Clio developer application. The one-click "listed" install variant (next section) is the one exception, and only for the login step.

Listed / one-click install variant (App Directory)

If you installed this connector via the Clio App Directory's one-click install instead of registering your own Clio developer application, you're using the *listed variant*. It uses one Clio application owned by Oktopeak, shared across every installing firm, instead of a separate application per firm. That means the application's client_secret cannot be distributed to your machine — it lives only on a small hosted token broker Oktopeak operates.

What that changes, precisely: matter data flows directly between your machine and Clio; only the login handshake passes through our token service. Every tool call — matters, contacts, documents, tasks, calendar, billing, everything — still goes directly from your machine to Clio's API, exactly as in the BYOC setup above. The broker never sees, stores, or logs any of it; it is only involved for the few seconds it takes to complete the OAuth login (and again, briefly, on token refresh). It stores nothing durable — no tokens, no session data survive past that single handshake.

Full data-flow documentation for security reviewers, including a sequence diagram and what the broker persists versus never persists, is in the token broker's repository: docs/DATA_FLOW.md.

Everything else — local AES-256-GCM token encryption, the audit log, and the 37 tools — is identical to the BYOC setup. Note that Clio's OAuth doesn't support requesting a narrower scope per login; the permissions your token carries are whatever the connecting Clio application was granted when it was registered in the Clio Developer Portal. For the listed app, that registration is kept to the minimum permission set the 37 tools need — the same principle you'd apply yourself when registering your own app for the BYOC setup. See Option C below for the resulting Claude Desktop config.

Trust Model

Three questions practitioners evaluating an AI tool for sensitive legal work should ask before installing.

Which Claude tier should we use?

The connector secures the transport between Clio and Claude. It does NOT change what Claude itself does with data once data enters a conversation. Claude's data handling depends on the tier you use, not on this connector.

  • Anthropic API with zero-data-retention (ZDR): no-training, no-retention terms, enabled at the organization level on the Anthropic API. A small firm can obtain it; it is not reserved for large enterprise contracts. This is the configuration we recommend for any work involving privileged client data.
  • Claude Enterprise / Team: explicit no-training guarantees, with ZDR available as an option. One way to get the configuration above, suited to firms that want a managed workspace rather than an API integration. Claude Enterprise is one option, not the only one.
  • **Claude Pro

Only the beginning is shown; read the rest in the repo

Ask PopNx