---
name: iblai-connect-clio
description: "Read and write Clio Manage data through the Clio Manage API (v4) and expose it to an ibl.ai agent as an MCP tool. Use when the user asks an agent to work with Clio Manage data, or to set up a Clio Manage MCP connection on ibl.ai."
metadata:
  kind: guide
---

# Clio Manage connector for AI agents

> A starting point maintained on ibl.ai at https://ibl.ai/developer/connectors/clio — not part of the iblai/vibe repository. Checked against Clio's documentation on October 20, 2026; test it against your own Clio Manage setup before you rely on it.

Clio Manage is cloud practice management software for law firms. It holds matters, contacts, time and expense activities, documents, calendar entries, tasks, notes, communications and billing records.

## Auth & conventions

- **API:** Clio Manage API (v4) (REST). JSON REST endpoints under /api/v4 for matters, contacts, activities, documents (with download), calendar entries, tasks, notes, communications, bills, custom fields and webhooks. A fields parameter selects attributes.
- **Base URL:** https://{region-host}/api/v4/ where region-host is app.clio.com (US), eu.app.clio.com, ca.app.clio.com or au.app.clio.com
- **Access:** Public, self-serve. Developers create an application in the Clio Developer Portal (developers.clio.com) to get a client key and secret, then each firm authorizes the app. Listing in the Clio App Directory has separate launch requirements.
- **Auth:** OAuth 2.0 authorization code. Authorize at https://{region-host}/oauth/authorize, exchange the code at /oauth/token. Codes last 10 minutes, access tokens 30 days, refresh tokens do not expire. Tokens only work in the region that issued them.
- **Limits:** Default 50 requests per minute per access token during peak hours, raised off-peak by region. 429 responses carry Retry-After; X-RateLimit-* headers on every response. Index actions return up to 200 records; follow meta.paging.next.
- Keep Clio Manage credentials in environment variables or the ibl.ai credential store. Never print a token in chat and never commit one to a file.
- Destructive or outward-facing calls are marked **Confirm with the user first** — do.

## Reads

- **Matters** — GET /api/v4/matters.json and /matters/{id}.json, plus a matter's contacts and client.
- **Contacts** — GET /api/v4/contacts.json for people and companies linked to matters.
- **Activities** — GET /api/v4/activities.json for time entries and expenses; filter by matter_id, limit 1-200.
- **Documents** — GET /api/v4/documents.json for metadata and /documents/{id}/download.json for file content.
- **Calendar entries and tasks** — GET /api/v4/calendar_entries.json and /api/v4/tasks.json.
- **Notes and communications** — GET /api/v4/notes.json and /api/v4/communications.json.

## Writes

- **Activities** — Create time or expense entries against a matter via /api/v4/activities.json.
- **Tasks and calendar entries** — Create or update tasks and calendar entries for a matter.
- **Notes** — Add notes to a matter or contact via /api/v4/notes.json.
- **Records (delete)** — DELETE on a resource removes it from the firm's Clio account. **Confirm with the user first.**

## Expose it to an ibl.ai agent (MCP)

Clio did not publish an MCP server of its own when this skill was checked. Host a small MCP server that wraps the calls above, then register it below.

First install the ibl.ai platform skills and connect your organization (writes `IBLAI_ORG`, `IBLAI_USERNAME` and `IBLAI_API_KEY` to `.env`):

```bash
npx skills add iblai/vibe --all
# then, in your coding agent:
/iblai-api-login
```

Every call below sends `Authorization: Api-Token $IBLAI_API_KEY`.

1. **Register the server** — `POST https://api.iblai.app/dm/api/ai-mentor/orgs/$IBLAI_ORG/users/$IBLAI_USERNAME/mcp-servers/` with `name`, `url`, `transport` (`sse` | `websocket` | `streamable_http`) and `auth_type` (`none` | `token` | `oauth2`). Capture the returned `id`.
   - Clio Manage supports per-user OAuth: `auth_type=oauth2` with `auth_scope=user` and a linked `oauth_service` makes each person connect their own account in the chat. It needs an `auth_{provider}` credential in the organization's credential store first.
2. **Create the connection** — `POST https://api.iblai.app/dm/api/ai-mentor/orgs/$IBLAI_ORG/users/$IBLAI_USERNAME/mcp-server-connections/` with `server`, `scope` (`platform` | `mentor` | `user`), `auth_type`, and either `credentials` + `authorization_scheme` or a `connected_service` id for OAuth. Credentials are masked on read; never send a masked value back.
3. **Enable it on the agent** — `GET https://api.iblai.app/dm/api/ai-mentor/orgs/$IBLAI_ORG/users/$IBLAI_USERNAME/mentors/{agent_id}/settings/`, add `mcp-tool` to `tool_slugs` and the server id to `mcp_servers`, then `PATCH` the full lists back. They are replaced, not merged.

Full reference: https://ibl.ai/developer/platform/mcp/mcp-connections and the `/iblai-api-agent-mcp` skill.

## Example prompts

- "List my open matters with no activity logged in the last 30 days"
- "Log 0.5 hours on the Smith v. Jones matter for drafting the motion to compel"
- "Show every task due this week across my matters"
- "Find the engagement letter document on matter 00123 and summarize it"

## Guardrails

- Matters, notes, documents and communications are client confidential and often covered by attorney-client privilege or work product protection.
- Request the narrowest Clio Manage scopes or role the task needs, and prefer a read-only credential for agents that only answer questions.
- Return the fields the user asked for, not whole records; do not paste personal data into chat that the user did not request.
- Before any write, show the user exactly what will change and wait for a yes.
- Respect the documented limits above: page through results and back off on rate-limit responses instead of retrying in a loop.

## References

- Clio Manage API authorization: https://docs.developers.clio.com/api-docs/clio-manage/authorization/
- Clio Manage API rate limits: https://docs.developers.clio.com/api-docs/clio-manage/rate-limits/
- Clio Manage API overview: https://docs.developers.clio.com/api-docs/clio-manage/
- This connector on ibl.ai: https://ibl.ai/developer/connectors/clio
- ibl.ai MCP server connections: https://ibl.ai/developer/platform/mcp/mcp-connections