NewCost control: a token allowance a month for each model choice — when one runs out, the cheaper one answers.See how it works
memtro
MCP server · Work management

Clio Manage MCP server

Clio Manage in any MCP client, through Memtro: Clio Manage does not publish this server. Memtro's Clio Manage connector reads Clio Manage through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read matters, clients and contacts, recorded time and expenses, bills and their balances, documents, calendar entries, tasks and logged correspondence from Clio Manage. Read-only: nothing in Clio is created or changed.

Reads

  • clio_mattersSearch and list matters (cases, files) in Clio Manage: the client, the responsible fee earner, the practice area…
  • clio_matterOne matter in full by id, with its client, fee earners, practice area and stage.
  • clio_contactsSearch clients and contacts in Clio Manage — people and companies alike, with email, phone and employer.
  • clio_timeRecorded time and expenses in Clio Manage: what was done, by whom, on which matter, how long it took…
  • clio_billsBills in Clio Manage with their state and outstanding balance: issued, due, paid or awaiting payment, and for which client.
  • clio_documentsDocuments filed against a matter in Clio Manage: name, category, type, size and when it arrived.
  • clio_calendarCalendar entries in Clio Manage: hearings, completions, deadlines and appointments, with the matter each belongs to.
  • clio_tasksTasks in Clio Manage: what is outstanding on a matter, who it is assigned to, its priority and when it is due.
  • clio_correspondenceCorrespondence logged against a matter in Clio Manage — the calls, emails and letters a fee earner recorded on the file…

Connect it

First connect Clio Manage on Dashboard → Connections, then add Memtro to your client once. The Clio Manage tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Clio Manage connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › Where are we with the Harper share purchase agreement, and what stage is it at?
  • › Which open matters have unbilled time on them, and how much?
  • › Which of Priya's matters are still open?
  • › Which client bills are awaiting payment, oldest first?
  • › What is in the diary on the Riverside matter in the next fortnight?

Questions

Is this an official Clio Manage MCP server?
No. It is Memtro's MCP server with Memtro's Clio Manage connector behind it: the connector reads Clio Manage through its API with the credentials you connect on Dashboard → Connections, and Clio Manage publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Clio Manage?
Not yet. Today every Clio Manage tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management