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.

Get Company (lawmatics_get-company)

Fetch a single company from Lawmatics by ID, including name, contact details, addresses, custom fields, and a `relationships` envelope of {id,type} pointers to related records (primary contact, contacts, prospects, tags, emails, phone numbers, addresses, notes, and the creating user).

Tool Input

companyIdstringrequired— ID of the company to fetch; a numeric string(pattern: ^\d+$)

Tool Output

idstringrequired— Lawmatics company ID
namestringnullrequired— Company name; null if unset
emailstringnullrequired— Primary email address; null if unset
addressstringnullrequired— Computed, formatted full address string; read-only; null if unset
citystringnullrequired— Primary address city; null if unset
statestringnullrequired— Primary address state/province; null if unset
postalCodestringnullrequired— Primary address ZIP/postal code; null if unset
countrystringnullrequired— Primary address country; null if unset
phoneNumberstringnullrequired— Primary phone number as stored; null if unset
addressesarrayrequired— All addresses associated with the company; empty array if none
[]object
idnumberrequired— Address ID
streetstringnullrequired— Street address line 1; null if unset
street2stringnullrequired— Street address line 2; null if unset
citystringnullrequired— Address city; null if unset
statestringnullrequired— Address state/province; null if unset
postalCodestringnullrequired— Address ZIP/postal code; null if unset
countrystringnullrequired— Address country; null if unset
labelstringnullrequired— Address label (e.g. Primary, Home, Work); 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
customFieldsarrayrequired— Account-defined custom fields on the company; empty array if none
[]object
idstringrequired— Custom field definition ID, as a numeric string
namestringnullrequired— Custom field display name; null if unset
fieldTypestringnullrequired— Custom field data type (e.g. text, date, select); null if unset
valueanyrequired— Raw custom field value; type varies by `fieldType`
formattedValueanyrequired— Display-formatted custom field value; type varies by `fieldType`
createdAtstringnullrequired— When the company was created, as an ISO 8601 timestamp; null if unknown
updatedAtstringnullrequired— When the company was last updated, as an ISO 8601 timestamp; null if unknown
relationshipsobjectrequired— JSON:API relationship pointers to related records as {id,type} stubs. Not materialized — follow a pointer by calling that resource's own get/find tool (e.g. type 'contact' -> get-contact, type 'user' -> get-user, type 'address' -> get-address).
primaryContactobjectnullrequired— Primary-contact pointer (live `type` "primary_contact"); null when unset
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
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
contactsarrayrequired— Contact pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
prospectsarrayrequired— Prospect (matter) pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
tagsarrayrequired— Tag pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
emailsarrayrequired— Email-address pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
phoneNumbersarrayrequired— Phone-number pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
addressesarrayrequired— Address pointers; empty if none. Distinct from the `addresses` attribute above, which carries the full nested address objects
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool
notesarrayrequired— Note pointers; empty if none
[]object
2 fields
idstringrequired— ID of the referenced Lawmatics record
typestringrequired— JSON:API record class of the reference; resolve it by calling that resource's own tool

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 Get Company tool do?

This page documents the Get Company tool (lawmatics_get-company). Fetch a single company from Lawmatics by ID, including name, contact details, addresses, custom fields, and a relationships envelope of {id,type} pointers to related records (primary contact, contacts, prospects, tags, emails, phone numbers, addresses, notes, and the creating user). It is one of the Lawmatics Companies 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

Get ContactGet RelationshipGet Mattercreate-companydelete-companylist-companies