Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Docketwise MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read contacts, matters, invoices and documents; create contacts, matters and notes in Docketwise.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http docketwise-mcp-by-usefulapi https://docketwise.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# docketwise_list_contacts, docketwise_get_contact, docketwise_list_matters and 17 more
Docketwise MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http docketwise-mcp-by-usefulapi https://docketwise.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
20 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The firm's contacts (clients, leads and institutions), 200 per page: id, name, company, email, lead flag, physical address. Filter by type. Use docketwise_get_contact for one contact with its notes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | Only people, or only institutions. |
| page | integer | no | Page number, from 1 (default 1). A page holds up to 200 records; see pagination in the reply for the next page. |
| limit | integer | no | Records to show from the page, 1-200 (default 100). Records beyond it on the same page are counted in omitted. |
One contact by id, with its address and notes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | The contact id (an integer, from docketwise_list_contacts). |
The firm's matters (cases), 200 per page: id, number, title, client_id, attorney, status, type, receipt number, priority date. Use docketwise_get_matter for one matter with its client, receipts and notes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1). A page holds up to 200 records; see pagination in the reply for the next page. |
| limit | integer | no | Records to show from the page, 1-200 (default 100). Records beyond it on the same page are counted in omitted. |
One matter by id, with its client, receipts, notes and assigned user ids.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | The matter id (an integer, from docketwise_list_matters). |
The USCIS receipts of one matter: receipt number, description, contact, status update type and time.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| matter_id | integer | yes | The matter id (an integer, from docketwise_list_matters). |
The firm's matter types, each with its matter statuses (workflow steps).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1). A page holds up to 200 records; see pagination in the reply for the next page. |
| limit | integer | no | Records to show from the page, 1-200 (default 200). Records beyond it on the same page are counted in omitted. |
The firm's matter statuses (workflow steps): name, duration, sort order.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1). A page holds up to 200 records; see pagination in the reply for the next page. |
| limit | integer | no | Records to show from the page, 1-200 (default 200). Records beyond it on the same page are counted in omitted. |
The firm's invoices, 200 per page: number, contact, status (paid/unpaid), type (bill, trust request, disbursement), dates, total and balance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1). A page holds up to 200 records; see pagination in the reply for the next page. |
| limit | integer | no | Records to show from the page, 1-200 (default 100). Records beyond it on the same page are counted in omitted. |
One invoice by id, with the matters it covers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | The invoice id (an integer, from docketwise_list_invoices). |
The charges (services, expenses, fees) on one invoice: amount, status, date, description, matter.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice_id | integer | yes | The invoice id (an integer, from docketwise_list_invoices). |
| page | integer | no | Page number, from 1 (default 1). A page holds up to 200 records; see pagination in the reply for the next page. |
| limit | integer | no | Records to show from the page, 1-200 (default 100). Records beyond it on the same page are counted in omitted. |
The firm's documents (metadata only, no file content), 200 per page: title, client, size, uploader, archived flag. Search by title.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Only documents whose title matches this text. |
| page | integer | no | Page number, from 1 (default 1). A page holds up to 200 records; see pagination in the reply for the next page. |
| limit | integer | no | Records to show from the page, 1-200 (default 100). Records beyond it on the same page are counted in omitted. |
One document's metadata by id (title, client, size, uploader, link to the document in Docketwise). No file content.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | The document id (an integer, from docketwise_list_documents). |
A temporary (one hour) download URL for one document's file. Anyone holding the link can download the file while it is valid: share it only with the user who asked.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | The document id (an integer, from docketwise_list_documents). |
The firm's Docketwise users (attorneys and staff): id, email, name. Use the ids as user_ids when creating a matter.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1). A page holds up to 200 records; see pagination in the reply for the next page. |
| limit | integer | no | Records to show from the page, 1-200 (default 200). Records beyond it on the same page are counted in omitted. |
Docketwise's country list: id, name, ISO code, phone code. Reference data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, from 1 (default 1). A page holds up to 200 records; see pagination in the reply for the next page. |
| limit | integer | no | Records to show from the page, 1-200 (default 200). Records beyond it on the same page are counted in omitted. |
WRITE: creates a new contact (person or institution) in the firm's Docketwise. Optionally with one address and one daytime phone. Creates a record; it does not check for duplicates.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| first_name | string | no | — |
| middle_name | string | no | — |
| last_name | string | no | — |
| string | no | — | |
| type | string | no | Default: Docketwise decides (a person). |
| lead | boolean | no | true = a lead, not yet a client. |
| address | object | no | An address of the contact. |
| phone | string | no | A daytime phone number. |
WRITE: changes the basic fields of one contact (name, company, email, lead flag). Only the fields you give are sent; each replaces the stored value. Addresses and phones are not changed here.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | The contact id (an integer, from docketwise_list_contacts). |
| first_name | string | no | — |
| middle_name | string | no | — |
| last_name | string | no | — |
| company_name | string | no | — |
| string | no | — | |
| type | string | no | — |
| lead | boolean | no | — |
WRITE: creates a new matter (case) for an existing client contact in the firm's Docketwise. The client_id is required; user_ids are the firm users assigned (docketwise_list_users).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_id | integer | yes | The client contact id (an integer, from docketwise_list_contacts). |
| title | string | no | — |
| number | string | no | The firm's matter number. |
| description | string | no | — |
| user_ids | array | no | Firm users assigned to the matter. |
WRITE: adds a note to a matter or to a client contact (give matter_id or client_id) in the firm's Docketwise.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| matter_id | integer | no | The matter id (an integer, from docketwise_list_matters). |
| client_id | integer | no | The client contact id (an integer, from docketwise_list_contacts). |
| title | string | no | — |
| content | string | yes | The note text. |
WRITE: replaces the title and/or text of an existing note. The previous text is not kept by this server. Docketwise requires matter_id or client_id again (the matter or client the note belongs to).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | The note id (an integer, from the notes of docketwise_get_matter or docketwise_get_contact). |
| matter_id | integer | no | The matter id (an integer, from docketwise_list_matters). |
| client_id | integer | no | The client contact id (an integer, from docketwise_list_contacts). |
| title | string | no | — |
| content | string | no | The new note text. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Docketwise MCP by usefulapi or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| docketwise_list_contacts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| docketwise_get_contact | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| docketwise_list_matters | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| docketwise_get_matter | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| docketwise_list_matter_receipts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| docketwise_list_matter_types | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| docketwise_list_matter_statuses | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| docketwise_list_invoices | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| docketwise_get_invoice | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| docketwise_list_invoice_charges | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| docketwise_list_documents | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| docketwise_get_document | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| docketwise_get_document_download_url | untrusted-input | untrusted-input: keyword "download", declares openWorldHint: true (interacts with entities outside the server) |
| docketwise_list_users | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| docketwise_list_countries | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| docketwise_create_contact | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| docketwise_update_contact | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| docketwise_create_matter | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| docketwise_create_note | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| docketwise_update_note | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.4.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Docketwise MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.