Weave
Sign InSign Up
View as .md ↗
Lawmatics

Lawmatics

MCP server · Practice Management · lawmatics.com · 40 categories · 177 tools

Lawmatics is a legal CRM, client intake, and marketing automation platform for law firms. This integration exposes contacts, companies, matters, billing (invoices, transactions, expenses, time entries), tasks, documents, events, and marketing data as governed MCP tools, scoped per member by access level.

List Matters (lawmatics_list-matters)

List matters (legal cases) from Lawmatics with optional pagination, filtering, and sorting. Rows carry case title, status, contact fields, and a `relationships` envelope of to-one {id,type} pointers (practice area, contact, company, attorneys, stage, source, ...); use get-matter for full details including to-many relationships.

Tool Input

pageinteger— Page number (1-based)(> 0)
filterobject— Optional single-field filter; one filter at a time
fieldstringrequired— Field to filter on. Most standard fields from the matter record work (e.g. status, case_title, first_name, estimated_value_cents); associations take an _id suffix (e.g. stage_id, practice_area_id)
operatorstring— Comparison operator. Omit to use the Lawmatics per-field default (= for ids/numbers/dates, ilike for strings). Use = for *_id fields. For like/ilike put % in the value where fuzzy matching should occur(enum: "=", "!=", "<", "<=", ">", ">=", "like", "ilike", "null", "not_null")
valuestringrequired— Value to compare against (ignored for null / not_null operators)
sortBystring— Column to sort by. id, created_at, and updated_at always work; most standard matter fields also work (e.g. actual_value_cents)
sortOrderstring— Sort direction; ascending or descending(enum: "asc", "desc")

Tool Output

mattersarrayrequired— Matters on this page of results. Rows carry case identity, status, contact fields, and to-one relationship pointers; use get-matter for the full record
[]object
idstringrequired— Lawmatics matter ID
caseTitlestringnullrequired— Title of the matter/case; null if unset
statusstringrequired— Matter pipeline status (e.g. pnc, hired, lost)
subStatusstringnullrequired— Name of the matter's sub-status; null if unset
firstNamestringnullrequired— First name of the matter's primary contact; null if unset
lastNamestringnullrequired— Last name of the matter's primary contact; null if unset
emailstringnullrequired— Primary email address of the matter's contact; null if unset
phonestringnullrequired— Primary phone number of the matter's contact; null if unset
createdAtstringrequired— When the matter was created, as an ISO 8601 timestamp
updatedAtstringrequired— When the matter was last updated, as an ISO 8601 timestamp
relationshipsobjectrequired— To-one JSON:API relationship pointers as {id,type} stubs. Not materialized — follow a pointer by calling that resource's own tool. List rows carry to-one pointers only; use get-matter for the full envelope incl. to-many (tasks, notes, files, ...).
11 fields
sourceobjectnullrequired— Lead source pointer; null when unset
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
stageobjectnullrequired— Pipeline stage pointer; null when unset
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
campaignobjectnullrequired— Marketing campaign pointer; null when unset
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
practiceAreaobjectnullrequired— Practice area pointer; null when unset
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
salespersonobjectnullrequired— Salesperson (user) pointer; null when unset
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
leadAttorneyobjectnullrequired— Lead attorney (user) pointer; null when unset
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
originatingAttorneyobjectnullrequired— Originating attorney (user) pointer; null when unset
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
ownedByobjectnullrequired— Owning user pointer; null when unset
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
createdByobjectnullrequired— Creating user pointer; null when unset
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
contactobjectnullrequired— Primary contact pointer; null when unset
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
companyobjectnullrequired— Linked company pointer; null when unset
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference (e.g. "user", "contact", "prospect", "firm"); resolve it by calling that resource's own get/find tool — this pointer is not materialized
paginationobjectrequired— Pagination metadata derived from the API `meta` envelope
totalPagesnumberrequired— Total number of pages available
limitPerPagenumberrequired— Maximum matters returned per page
totalEntriesnumberrequired— Total number of matters across all pages

We're Adding More Lawmatics Tools Constantly!

Don't see a specific Lawmatics tool you need? Email support@weave.legal and we can add it.

Lawmatics Frequently Asked Questions

What does the List Matters tool do?

This page documents the List Matters tool (lawmatics_list-matters). List matters (legal cases) from Lawmatics with optional pagination, filtering, and sorting. Rows carry case title, status, contact fields, and a relationships envelope of to-one {id,type} pointers (practice area, contact, company, attorneys, stage, source, ...); use get-matter for full details including to-many relationships. It is one of the Lawmatics Matters tools, invoked through your firm's Weave MCP connection and available to members whose access level permits it.

What is the Lawmatics integration?

The Lawmatics integration connects your firm's Lawmatics account to Weave. Lawmatics is a legal CRM, client intake, and marketing automation platform for law firms. This integration exposes contacts, companies, matters, billing (invoices, transactions, expenses, time entries), tasks, documents, events, and marketing data as governed MCP tools, scoped per member by access level. It groups 177 tools into 40 categories, exposed through your firm's Weave MCP connection and filtered per member by access level.

How does my firm connect Lawmatics to Weave?

An admin connects Lawmatics once for the whole firm via OAuth. Every member then works through that single connection; there is no per-user Lawmatics login.

Do I need to install or configure anything locally?

No. Weave is fully hosted, so there is nothing to install, run, or maintain on your own machines. An admin connects Lawmatics once from the Weave console through a secure OAuth handshake, and your credentials are encrypted at rest and stay inside Weave's infrastructure. After that, each member simply points their AI assistant at your firm's Weave MCP endpoint, and the tools they are allowed to use appear automatically based on their access level.

Can everyone on my team use every tool?

No. Tools are exposed per member by access level, so each person only sees the Lawmatics tools their role permits.

Are changes made through these tools reversible?

Reads are always safe. Deletes are irreversible: they remove the record from Lawmatics permanently.

How are money amounts represented?

All monetary values (expenses, transactions, invoices, time-entry rates) are integer cents; for example, 50000 means $500.00.

Related Tools

List Practice AreasList Sub StatusesList PipelinesList Companiescontactscreate-matter