LitCo agent connector — Review, Research & Files for Cursor, Claude Code and any MCP agent

This connector lets your AI agent work in LitCo Review (document review), LitCo Research (case law) and LitCo Files (matter files) as you.

It is a small stdio MCP server that calls the LitCo API with your own connection token. Every request is checked on the server against:

• your live roles;

• your firm's agent-connection policy;

• the products and matters you chose when you created the connection.

The agent can do only what you can do in LitCo in the browser. Administration, exports, launching review runs and adding people are browser-only, so no agent can do them. Every action is audited as you, through the connection.

Every agent your Firm admin enables gets the same tools and the same access. There is no per-agent read-only mode on the server, and writes (tag, note, thread post, upload) take effect immediately, as in LitCo.

Credentials

litco-mcp login saves the token to ~/.config/litco/connection.json with mode 0600. Nothing else is written anywhere.

Never commit a token. Never set a personal lku_ token in a team-wide plugin setting: it would make everyone act as you.

Related MCP server: Supabase User MCP

Install

Cursor

1. Install the LitCo plugin from the Cursor marketplace, or add this repository as a plugin.

2. In a terminal, run: npx -y github:yavarb/litco-cursor-plugin login --client cursor (or node <plugin-dir>/dist/litco-mcp.mjs login --client cursor).

3. Open the link it prints, check the code, choose products and matters, and approve.

4. Restart the MCP server in Cursor.

Claude Code

In Claude Code:

/plugin marketplace add yavarb/litco-cursor-plugin
/plugin install litco@litco

Then sign in from a terminal:

npx -y github:yavarb/litco-cursor-plugin login --client claude-code

Or wire the server by hand, without the plugin:

claude mcp add litco -e LITCO_CONNECTION_TOKEN=lku_… -- node /path/to/dist/litco-mcp.mjs

Any other MCP client

Run node dist/litco-mcp.mjs as a stdio server, with LITCO_CONNECTION_TOKEN in its environment (or after login).

Grokbot (litco-agent)

Personal mode uses the same token. Set LITCO_CONNECTION_TOKEN=lku_… (and LITCO_API_BASE_URL). Grokbot then sends Authorization: Bearer lku_… and no acting-user headers: a connection token names one person and cannot act for anyone else.

Tools

With a firm key (lkf_), only the LitCo Research tools are registered.

A document's responsiveness (Responsive / Not Responsive / Unsure), privilege and confidentiality are its coding: set or clear them with litkit_set_coding. LitCo refuses responsiveness tags through litkit_tag_document.

Billing tools work on your own time and expense entries (and everyone's on a matter you administer for billing). A change to more than one entry, a delete, or a move to another matter first comes back as a dry run with a preview and a confirm_token; call again with the same arguments and that token to apply it. Every applied change returns a change_id that billing_undo_change reverts. A connection pinned to matters cannot reach Billing.

Skills in skills/ teach the agent the workflows: getting started, LitCo Research, LitCo Review and LitCo Files.

Commands

litco-mcp                 run the stdio MCP server
litco-mcp login [--client cursor|claude-code|grokbot|other] [--name "…"]
litco-mcp whoami          show who the connection acts as
litco-mcp logout          forget the saved token (revoke it in LitCo too)

Revoking

Revoke a connection in LitCo → Settings → Connections. Your Firm admin can revoke any connection, or all of a person's connections, from Admin → Billing → API keys.

A connection also stops working by itself in any of these cases:

• it expires (at most a year; your firm may set less);

• your password changes;

• your role no longer allows connections;

• your firm turns connections off.

Develop

npm install
npm run typecheck && npm test
npm run build        # bundles src/ → dist/litco-mcp.mjs (committed, so plugin installs need no npm install)

License

Apache-2.0. See LICENSE.