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 Tasks (lawmatics_list-tasks)

List tasks from Lawmatics with optional pagination, filtering, and sorting. Filter by the associated matter/contact/company/client id, an assigned user id, or task fields like done, priority, and due_date. Each row carries a `relationships` envelope with a to-one `taskable` {id,type} pointer to the associated record; use get-task for the full envelope including to-many pointers (users, documents, files, subtasks, comments).

Tool Input

pageinteger— Page number (1-based)(> 0)
filterobject— Optional single-field filter; one filter at a time
fieldstringrequired— Field to filter on: matter_id/prospect_id (numeric id of the associated matter), contact_id, company_id, client_id, user_id (numeric id of an assigned firm user), name (task name), done (true/false), priority (high/medium/low), due_date, created_at, or updated_at (dates)(enum: "matter_id", "prospect_id", "contact_id", "company_id", "client_id", "user_id", "name", "done", "priority", "due_date", "created_at", "updated_at")
operatorstring— Comparison operator. Omit to use the Lawmatics per-field default (= for ids/booleans/dates, ilike for strings). Use = for id fields and a range operator (e.g. <) for due_date(enum: "=", "!=", "<", "<=", ">", ">=", "like", "ilike", "null", "not_null")
valuestringrequired— Value to compare against (ignored for null / not_null operators)
sortBystring— Column to sort by(enum: "id", "created_at", "updated_at", "due_date", "name", "priority")
sortOrderstring— Sort direction; ascending or descending(enum: "asc", "desc")

Tool Output

tasksarrayrequired— Tasks on this page of results
[]object
idstringrequired— Unique ID of the task
namestringrequired— Name/title of the task
descriptionstringnullrequired— Description of the task; null if unset
dueDatestringnullrequired— ISO 8601 timestamp the task is due; null if no due date is set
donebooleanrequired— Whether the task is completed
statusstringnullrequired— Read-only display status (e.g. "No Status"); null when the projection omits it
prioritystringrequired— Task priority as returned by the API (high, medium, low)
tagsarrayrequired— Tags attached to this task
1 field
[]object
3 fields
idstringrequired— Unique ID of the tag
namestringrequired— Name of the tag
colorstringnullrequired— Hex display color of the tag; null if unset
assignedByIdstringnullrequired— ID of the firm user who assigned the task; null if unset or omitted
recurrenceRuleobjectnullrequired— Recurrence rule with inner keys preserved exactly as the API returns them (type, frequency, weekday booleans, and an end-date key that may appear as endDate or end_date); null when the task does not recur or the projection omits it
1 field
[key: string]stringnumberbooleannull
createdAtstringnullrequired— When the task was created, as an ISO 8601 timestamp; null if unknown
updatedAtstringnullrequired— When the task was last updated, as an ISO 8601 timestamp; null if unknown
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 the to-one pointer only; use get-task for the full envelope incl. to-many (users, documents, files, subtasks, comments).
1 field
taskableobjectnullrequired— Associated record (matter/prospect, contact, or company) pointer; null for unattached tasks
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
paginationobjectnullrequired— Pagination metadata from the API response; null when the endpoint returns no meta envelope
totalPagesnumbernullrequired— Total number of pages available; null if not reported
limitPerPagenumbernullrequired— Maximum tasks returned per page; null if not reported
totalEntriesnumbernullrequired— Total number of tasks across all pages; null if not reported

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 Tasks tool do?

This page documents the List Tasks tool (lawmatics_list-tasks). List tasks from Lawmatics with optional pagination, filtering, and sorting. Filter by the associated matter/contact/company/client id, an assigned user id, or task fields like done, priority, and due_date. Each row carries a relationships envelope with a to-one taskable {id,type} pointer to the associated record; use get-task for the full envelope including to-many pointers (users, documents, files, subtasks, comments). It is one of the Lawmatics Tasks 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 SubtasksList Task StatusesList Eventscommentscreate-taskdelete-task