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.

Find Contact By Phone (lawmatics_find-contact-by-phone)

Fuzzy-find a single contact in Lawmatics by phone number, including a `relationships` envelope of {id,type} pointers to related records (company, prospects/matters, emails, phone numbers, addresses, notes, files, folders, tags, and more). Returns `{ match: <entity> }` on a hit and `{ match: null }` when no record matches. `match: null` is a normal empty result, not an error — do not retry.

Tool Input

phoneNumberstringrequired— Phone number to search for. The server normalizes it before matching (strips all non-digits and tries with and without a leading 1 for US country codes), so any common phone format is accepted.(min length: 1)

Tool Output

matchobjectnullrequired— The single best matching contact, or null if nothing matched. Returns `{ match: <entity> }` on a hit and `{ match: null }` when no record matches. `match: null` is a normal empty result, not an error — do not retry.
idstringrequired— Lawmatics contact ID
firstNamestringnullrequired— Contact's first/given name; null if unset
lastNamestringnullrequired— Contact's last/family name; null if unset
emailstringnullrequired— Primary email address; null if unset
phonestringnullrequired— Primary phone number as stored; null if unset
createdAtstringnullrequired— When the contact was created, as an ISO 8601 timestamp; null if unknown
updatedAtstringnullrequired— When the contact 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 'company' -> get-company, type 'prospect' -> get-matter, type 'user' -> get-user).
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
clientobjectnullrequired— Linked client 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
customContactTypeobjectnullrequired— Custom contact-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
prospectsarrayrequired— Prospect (matter) pointers; empty if none
1 field
[]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
1 field
[]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
1 field
[]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
1 field
[]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
1 field
[]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
1 field
[]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
filesarrayrequired— File pointers; empty if none
1 field
[]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
foldersarrayrequired— Folder pointers; empty if none
1 field
[]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 Find Contact By Phone tool do?

This page documents the Find Contact By Phone tool (lawmatics_find-contact-by-phone). Fuzzy-find a single contact in Lawmatics by phone number, including a relationships envelope of {id,type} pointers to related records (company, prospects/matters, emails, phone numbers, addresses, notes, files, folders, tags, and more). Returns { match: <entity> } on a hit and { match: null } when no record matches. match: null is a normal empty result, not an error, do not retry. It is one of the Lawmatics Lookups 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

matterspipeline-stagespractice-areasfind-company-by-emailfind-company-by-namefind-company-by-phone