Weave
Sign InSign Up
View as .md ↗
Lawmatics

Lawmatics | List Addresses

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.

lawmatics_list-addresses

List addresses from Lawmatics with optional pagination, filtering, and sorting. Prefer a filter when possible — the unfiltered firm-wide list is slow and may time out. Filter by addressable_id (the contact/matter/company the address belongs to), addressable_type, label, or created_at — the original fields. Also filter by street/city/state/zipcode/country (string columns) or by contact_id/company_id (shortcuts selecting the owning contact's/company's addresses; = only). Each row carries a `relationships` envelope with the owning `addressable` record as a to-one {id,type} pointer (a contact, company, matter, event, or the firm itself); use get-address for the full envelope including associated locations.

Tool Input

pageinteger— Page number (1-based)(> 0)
filterobject— Optional single-field filter; one filter at a time
fieldstringrequired— Field to filter on. addressable_id (numeric id of the contact/matter/company the address belongs to), addressable_type (owning record type), label (address label, e.g. Home / Work), created_at (date) — the original fields, all operators accepted. street/city/state/zipcode/country are string columns (= != like ilike null not_null). contact_id/company_id are shortcuts selecting the owning contact's/company's addresses — only = (or an omitted operator) is accepted, with a numeric id value(enum: "addressable_id", "addressable_type", "label", "created_at", "street", "city", "state", "zipcode", "country", "contact_id", "company_id")
operatorstring— Comparison operator. Omit to use the Lawmatics per-field default. Allowed per field: addressable_id/addressable_type/label/created_at accept all 10 operators (unchanged); street/city/state/zipcode/country accept = != like ilike null not_null; contact_id/company_id accept only = (the operator is ignored live, so anything else is rejected at the boundary)(enum: "=", "!=", "<", "<=", ">", ">=", "like", "ilike", "null", "not_null")
valuestring— Value to compare against. Required for the comparison operators; must be omitted for the null / not_null presence operators. contact_id/company_id require a numeric id
sortBystring— Column to sort by(enum: "id", "created_at", "updated_at")
sortOrderstring— Sort direction; ascending or descending(enum: "asc", "desc")

Tool Output

addressesarrayrequired— Addresses on this page of results
[]object
idstringrequired— Unique ID of the address
addressTypestringrequired— Address label (e.g. Home, Work, Mailing)
streetstringnullrequired— Street address line 1; null if unset
street2stringnullrequired— Street address line 2 (apt, suite, etc.); null if unset
citystringnullrequired— City; null if unset
statestringnullrequired— State or province; null if unset
postalCodestringnullrequired— Postal/ZIP code; null if unset
countrystringnullrequired— Country; null if unset
fullAddressstringnullrequired— Full formatted single-line address; null if unset
createdAtstringnullrequired— When the address was created, as an ISO 8601 timestamp; null if unknown
updatedAtstringnullrequired— When the address 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 owning `addressable` pointer only; use get-address for the full envelope incl. to-many locations.
1 field
addressableobjectnullrequired— Owning record pointer; null when unlinked. Polymorphic — the `type` is an open string (e.g. "contact", "company", "prospect" for a matter, "registerable_event", "firm"); resolve it by calling that record's own get/find tool
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
limitPerPagenumbernullrequired— Maximum addresses returned per page; null if not reported
totalEntriesnumbernullrequired— Total number of addresses 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 Addresses tool do?

This page documents the List Addresses tool (lawmatics_list-addresses). List addresses from Lawmatics with optional pagination, filtering, and sorting. Prefer a filter when possible, the unfiltered firm-wide list is slow and may time out. Filter by addressable_id (the contact/matter/company the address belongs to), addressable_type, label, or created_at, the original fields. Also filter by street/city/state/zipcode/country (string columns) or by contact_id/company_id (shortcuts selecting the owning contact's/company's addresses; = only). Each row carries a relationships envelope with the owning addressable record as a to-one {id,type} pointer (a contact, company, matter, event, or the firm itself); use get-address for the full envelope including associated locations. It is one of the Lawmatics Addresses 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 Email AddressesList Phone NumbersList Contactscompaniescreate-addressdelete-address