Clio-mcp Server

Clio-mcp is an MCP integration. Connect Claude to Clio: 34 tools for matters, custom fields, notes, documents, folders, billing.

Packages and local setup

The published npm package is @oktopeak/clio-mcp, version 2.2.0. Its declared MCP transport is stdio.

The package declares CLIO_CLIENT_ID (required): Client ID from your Clio developer application (Settings → Developer Applications); CLIO_CLIENT_SECRET (required): Client Secret from your Clio developer application; ENCRYPTION_KEY: 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 the OS keychain on first use.; CLIO_REDIRECT_PORT: Local port for the OAuth callback listener (default: 5678). Change if 5678 is in use.; CLIO_REGION: 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 match the server your firm logs in to. Any other value stops startup.; READ_ONLY: Optional. 'true', '1' or 'yes' leaves the nine write tools (create_matter, create_note, create_task, update_task, complete_task, create_calendar_entry, log_time_entry, create_activity, upload_document) unregistered so Claude can read Clio but never change it. Works on both transports.; CLIO_API_BASE: 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: Override the OAuth authorization endpoint (e.g. https://eu.app.clio.com/oauth/authorize).; CLIO_TOKEN_URL: Override the OAuth token endpoint (e.g. https://eu.app.clio.com/oauth/token)..

The package declares TOKEN_BROKER_URL (required): URL of Oktopeak's hosted token broker for the Clio App Directory listed install. Do not set CLIO_CLIENT_ID/CLIO_CLIENT_SECRET alongside this — the shared app's secret lives only on the broker, never on this machine.; ENCRYPTION_KEY: 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 the OS keychain on first use..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 2.2.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.