rocketmatter-mcp
MCP server for Rocketmatter — legal practice management
from Claude Desktop in natural language, over the official ProfitSolv LCS /v1
Integration API with a scoped OAuth integration.
No password login: the server authorizes once in the browser, then refreshes its own token forever. It never trips Rocket Matter's single-session-per-user limit, so it won't log you out of your Rocket Matter browser session while it runs.
What you can do
The LCS /v1 Integration API covers the core practice-management entities:
- Matters — list, get, create, update, delete
- Clients & Contacts — full CRUD
- Time entries & Expenses — full CRUD (log and edit billable time and costs)
- Invoices — list, get, create, update, delete
- Payments — list and record
- Transactions — list (by matter or bank), get, create, update, delete
- Documents — list (read-only)
- Users / timekeepers — list, get
- UTBMS codes — per matter
Not covered by the /v1 API
The /v1 Integration API is narrower than Rocket Matter's internal UI. These are
not available and their tools fail loudly (rather than returning nothing): firm
financial summary, timekeeper time summaries, bank/chart-of-accounts enumeration,
the two-step invoice-generation flow, accounts payable, lookup/defaults endpoints,
and tasks, timers, calendar, tags, trust, rates, firm roles, tax/discount, phone
messages, internal chat, workflow, reports, recurring billing, matter templates, and
court rules.
Requirements
- Python 3.10+
- Python MCP SDK >=2.2,<3 (protocol revision 2026-07-28)
- Claude Desktop (or any MCP-compatible client)
- A Rocket Matter account and a registered OAuth integration (API key + OAuth client ID/secret) for the ProfitSolv LCS Integration API
Installation
pip install rocketmatter-mcp
Setup
rocketmatter-mcp-setup
Before setup, the firm must register http://127.0.0.1:8771/callback as an
OAuth redirect with Rocket Matter / ProfitSolv. To use another port, set
ROCKETMATTER_REDIRECT_URI to the exact registered HTTP loopback URI (127.0.0.1,
explicit port and callback path). localhost, IPv6 and external callbacks are rejected.
The wizard:
- Stores the integration's API key, OAuth client ID, and client secret in the OS keyring (with a private file fallback).
- Binds the configured local callback before printing the authorization URL. Open that URL in your browser and click Allow.
- Receives the callback locally and checks the session's random
statebefore exchanging the code. It stops if the port is occupied or consent times out. - Atomically caches access and refresh tokens in
~/.rocketmatter-mcp/tokens.json, created with mode0600before writing any secret bytes.
Authorization codes are never accepted in command-line arguments or environment variables. The callback handles them automatically.
After that, the client refreshes its own access token with the long-lived refresh token — no browser, no password — so you won't be prompted again unless the refresh token is revoked.
Verify:
rocketmatter-mcp-verify
Claude Desktop Configuration
{
"mcpServers": {
"rocketmatter": {
"command": "rocketmatter-mcp"
}
}
}
Credential storage
By default credentials are stored in your operating system's native secret store
via the cross-platform keyring library:
| OS | Backend |
|---|---|
| macOS | Keychain |
| Windows | Credential Manager |
| Linux | Secret Service (GNOME Keyring / KWallet) |
With a working keyring backend, secrets are saved under the service name
rocketmatter-mcp and are not written to the fallback file.
File fallback. On a host with no keyring backend (e.g. a headless Linux box
without Secret Service), or if you set ROCKETMATTER_MCP_USE_KEYRING=0, credentials
fall back to a ~/.rocketmatter-mcp/.env file with 0600 permissions.
On Windows, the file is stored in the user's profile and protected by Windows'
default per-user access rules. On POSIX, files are created with 0600 permissions
and writes fail closed if private permissions cannot be established.
Read order. Credentials resolve in the order OS keyring → process environment
→ .env file.
Authentication notes
The server uses the ProfitSolv LCS /v1 Integration API with a scoped OAuth
integration:
- Consent once (
/OAuth/authorize→Allow) to obtain an authorization code. - Exchange the code at
{base}/api/ext/auth/token(grant_type=authorization_code) for anaccess_token(~5h) + a long-livedrefresh_token. - Data calls go to the LCS
/v1host with two headers:X-Api-Key: <app key>andX-User-Token: <access token>. - Refresh (
grant_type=refresh_token) renews the access token without a password login, so the user's Rocket Matter browser session is never bumped.
Hosts are overridable via ROCKETMATTER_BASE_URL (OAuth host — Rocket Matter
app.rocketmatter.net, CosmoLex law.cosmolex.com) and ROCKETMATTER_API_BASE_URL
(the LCS /v1 data host).
Example usage in Claude
"List my matters"
"Create a client named Acme Holdings"
"Log a time entry on matter "
"Show open invoices and recent payments"
"List the firm's users"
License
MIT — see LICENSE.
Endpoint configuration
OAuth accepts only https://app.rocketmatter.net. The data endpoint accepts only
the two exact ProfitSolv LCS production/sandbox hosts listed in
rocketmatter_mcp/endpoint_validation.py; arbitrary Azure tenants are rejected.
Both endpoint settings reject userinfo, paths, query strings, fragments and ports
other than 443. A new vendor endpoint requires an allowlist update after verification.
The public LCS sandbox Swagger document
identifies the ProfitSolv LCS gateway. The legacy Rocket Matter reference
describes a different API; it does not establish additional LCS hosts.
Metadata
Release files for rocketmatter-mcp 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rocketmatter_mcp-0.5.0.tar.gz | 151.1 kB | Without provenance | Details for rocketmatter_mcp-0.5.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rocketmatter_mcp-0.5.0-py3-none-any.whl | Python 3 | none | any | Details for rocketmatter_mcp-0.5.0-py3-none-any.whl |
Total release size: 187.7 kB
Release files / rocketmatter_mcp-0.5.0.tar.gz
| Download URL | rocketmatter_mcp-0.5.0.tar.gz |
|---|---|
| Size | 151.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c8e217170d05d7817bd11c84eb43955ed5624ecc22d594ff5404c9a989cc22ee
|
|
BLAKE2b-256 checksum How to use checksums |
37e3f985697b30a19f042fb77102bb36868c57b79cb13ea096c49a7c67842be1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.4 {"installer":{"name":"uv","version":"0.12.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / rocketmatter_mcp-0.5.0-py3-none-any.whl
| Download URL | rocketmatter_mcp-0.5.0-py3-none-any.whl |
|---|---|
| Size | 36.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c0e4181785a7e90af927c1d86e543c5097cbd6c09c32df977725e2ceff79681b
|
|
BLAKE2b-256 checksum How to use checksums |
bf7e1104f9b5026afe21a5b36ad81f01261debec807c8f0eef03ff83f1cb92b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.4 {"installer":{"name":"uv","version":"0.12.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for rocketmatter-mcp 0.5.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.