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 Time Entries (lawmatics_list-time-entries)

List time entries from Lawmatics with optional pagination and sorting. Time entries record time spent on a matter or contact; durations are in hours and hourly rates are in integer cents. Each row carries a `relationships` envelope of to-one {id,type} pointers (the matter or contact billed to, staff and creating users, activity type, invoice).

Tool Input

pageinteger— Page number (1-based)(> 0)
sortBystring— Column to sort by(enum: "id", "created_at", "updated_at")
sortOrderstring— Sort direction; ascending or descending(enum: "asc", "desc")

Tool Output

timeEntriesarrayrequired— Time entries on this page of results
[]object
idstringrequired— Unique ID of the time entry
descriptionstringnullrequired— Description of the work performed; null if unset
durationnumberrequired— Duration in hours as a float (e.g. 1.5 = 1 hour 30 minutes), NOT minutes
durationRoundednumbernullrequired— Duration rounded to the firm's billing increment, in hours; null if not reported
billablebooleannullrequired— Whether the time is billable; null if not reported
rateFlatFeebooleannullrequired— Whether this is a flat-fee entry; null if not reported
rateCentsintegernullrequired— Hourly rate in integer cents (e.g. 12000 = $120.00/hr); null if not reported
rateCurrencystringnullrequired— ISO currency code of the rate (e.g. "USD"); null if not reported
runningSincestringnullrequired— When the entry's live timer started, as an ISO 8601 timestamp; null when no timer is running
startedAtstringnullrequired— When the time entry started, as an ISO 8601 timestamp; null if unset
completedAtstringnullrequired— When the time entry completed, as an ISO 8601 timestamp; null while incomplete (only completed entries can be added to invoices)
createdAtstringrequired— When the time entry record was created, as an ISO 8601 timestamp
updatedAtstringrequired— When the time entry record 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 (e.g. type 'user' -> get-user, type 'prospect' -> get-matter, type 'contact' -> get-contact, type 'invoice' -> get-invoice).
5 fields
activityTypeobjectnullrequired— Billing activity type 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
contactableobjectnullrequired— Pointer to the record the time is billed to; type is "prospect" for a matter or "contact" for a contact; null when unassociated
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— Pointer to the user who created the record; null when unattributed
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
invoiceobjectnullrequired— Pointer to the invoice this entry is attached to; null when not invoiced
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
staffobjectnullrequired— Pointer to the user who performed the time entry; null when unattributed
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 time entries returned per page
totalEntriesnumberrequired— Total number of time entries across all pages

We're Adding More Lawmatics Tools Constantly!

Don't see a specific Lawmatics tool you need? Email [email protected] and we can add it.

Lawmatics Frequently Asked Questions

What does the List Time Entries tool do?

This page documents the List Time Entries tool (lawmatics_list-time-entries). List time entries from Lawmatics with optional pagination and sorting. Time entries record time spent on a matter or contact; durations are in hours and hourly rates are in integer cents. Each row carries a relationships envelope of to-one {id,type} pointers (the matter or contact billed to, staff and creating users, activity type, invoice). It is one of the Lawmatics Time Entries 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