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 Contact (lawmatics_get-contact)

Fetch a single contact from Lawmatics by ID, including standard fields, custom fields, and a `relationships` envelope of {id,type} pointers to related records (creating user, client, company, custom contact type, matters, tags, emails, phone numbers, addresses, notes, files, folders).

Tool Input

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

Tool Output

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
emailAddressstringnullrequired— Alternate email field returned by the API; may duplicate or differ from `email`; null if unset
phonestringnullrequired— Primary phone number as stored; null if unset
phoneNumberstringnullrequired— Alternate phone field returned by the API; may duplicate or differ from `phone`; null if unset
birthdatestringnullrequired— Date of birth as an ISO 8601 date; null if unset
namePrefixstringnullrequired— Honorific before the name (e.g. Mr., Dr.); null if unset
middleNamestringnullrequired— Contact's middle name; null if unset
nameSuffixstringnullrequired— Suffix after the name (e.g. Jr., III); null if unset
informalNamestringnullrequired— Preferred informal/nickname for the contact; null if unset
employerstringnullrequired— Contact's employer or organization; null if unset
occupationstringnullrequired— Contact's occupation or job role; null if unset
citizenshipstringnullrequired— Contact's citizenship; null if unset
biostringnullrequired— Free-text biography or notes about the contact; null if unset
titlestringnullrequired— Job title; null if unset
hobbiesstringnullrequired— Free-text hobbies or interests; null if unset
socialSecuritystringnullrequired— Social Security number as stored; null if unset
agenumbernullrequired— Contact's age in years; null if unset
driverLicensestringnullrequired— Driver's license number as stored; null if unset
genderstringnullrequired— Contact's gender as stored; null if unset
maritalStatusstringnullrequired— Contact's marital status as stored; null if unset
timezonestringnullrequired— Contact's timezone identifier; null if unset
trackingSourceIdstringnullrequired— ID of the tracking source the contact came from; null if unset
dateOfLastContactstringnullrequired— Date of the most recent contact as an ISO 8601 date; null if never contacted
daysSinceLastContactnumbernullrequired— Whole days elapsed since the last contact; null if never contacted
photoUrlstringnullrequired— URL of the contact's photo; null if unset
contactTypestringnullrequired— Contact classification as stored (e.g. lead, client); 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
customFieldsarrayrequired— Account-defined custom fields on the contact; 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`
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 'prospect' -> get-matter, type 'user' -> get-user, type 'company' -> get-company).
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
clientobjectnullrequired— Linked client (matter) 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
companyobjectnullrequired— Linked company 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
customContactTypeobjectnullrequired— Custom contact-type 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
prospectsarrayrequired— Matter (prospect) 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
[]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
filesarrayrequired— File 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
foldersarrayrequired— Folder 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 support@weave.legal and we can add it.

Lawmatics Frequently Asked Questions

What does the Get Contact tool do?

This page documents the Get Contact tool (lawmatics_get-contact). Fetch a single contact from Lawmatics by ID, including standard fields, custom fields, and a relationships envelope of {id,type} pointers to related records (creating user, client, company, custom contact type, matters, tags, emails, phone numbers, addresses, notes, files, folders). It is one of the Lawmatics Contacts 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