Local MCP connector that lets Claude read live data from Clio Practice Management and perform limited write actions on tasks and notes. It uses OAuth, stores tokens encrypted locally, and logs tool calls for audit purposes.
From the registry: Connect Claude to Clio with 15 tools for matters, contacts, tasks, billing, and more.
$ node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"$ git clone https://github.com/oktopeak/clio-mcp.git && cd clio-mcp && npm install && npm run buildhttps://github.com/oktopeak/clio-mcpPlease install the `clio-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Install Node.js 18 or later** — Node.js 18+ is required to install dependencies and run the MCP server. (https://nodejs.org/en/download/)
- **Have a Clio account with developer application access** — You need a Clio account and permission to create a developer application in Clio. (https://www.clio.com)
- **Create a Clio API application** — In Clio, go to Settings → Developer Applications, add an application, set the redirect URI exactly to http://127.0.0.1:5678/callback (or your chosen redirect port), and copy the Client ID and Client Secret.
- **Generate an encryption key** — Generate a 64-character hex key used to encrypt stored OAuth tokens locally. Run: `node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"`
- **Clone and build the server** — Clone the repository, install dependencies, and build the project before configuring your MCP client. Run: `git clone https://github.com/oktopeak/clio-mcp.git && cd clio-mcp && npm install && npm run build` (https://github.com/oktopeak/clio-mcp)
Canonical MCP server config (stdio transport):
- command: `node`
- args: ["<full-path-to-clio-mcp>/build/index.js"]
- required environment variables:
- `CLIO_CLIENT_ID`: Client ID from your Clio developer application. (example: `<your-clio-client-id>`)
- `CLIO_CLIENT_SECRET`: Client Secret from your Clio developer application. (example: `<your-clio-client-secret>`)
- `ENCRYPTION_KEY`: 64-character hex key used to encrypt stored Clio OAuth tokens on disk. (example: `<your-64-character-hex-encryption-key>`)
- optional environment variables:
- `CLIO_REDIRECT_PORT`: Local port for the OAuth callback. Default is 5678. If changed, the redirect URI in your Clio developer application must match. (example: `<your-redirect-port>`)
- `CLIO_API_BASE`: Override the Clio API base URL for regional Clio deployments such as EU, Canada, or Australia. (example: `<your-clio-api-base-url>`)
- `CLIO_AUTH_URL`: Override the Clio OAuth authorization endpoint for regional Clio deployments. (example: `<your-clio-auth-url>`)
- `CLIO_TOKEN_URL`: Override the Clio OAuth token endpoint for regional Clio deployments. (example: `<your-clio-token-url>`)
Note: The README only shows a local build/run path, not an npm/npx package. Authentication is completed after startup by asking the client to run the authenticate tool, which opens a browser for Clio OAuth. Default redirect URI is http://127.0.0.1:5678/callback. For regional Clio environments, set CLIO_API_BASE, CLIO_AUTH_URL, and CLIO_TOKEN_URL accordingly.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.CLIO_CLIENT_IDrequiredClient ID from your Clio developer applicationCLIO_CLIENT_SECRETrequiredClient Secret from your Clio developer applicationENCRYPTION_KEYrequired64-character hex key for encrypting stored tokensMeta Ads MCP (Facebook + Instagram) - analyze performance, manage budgets, pause campaigns.