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.

Create Contact (lawmatics_create-contact)

Create a contact in Lawmatics. The response echoes 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

firstNamestring— Contact's first name
lastNamestring— Contact's last name
emailstring— Primary email address
phonestring— Primary phone number
namePrefixstring— Name prefix (e.g. Mr, Ms, Dr)
middleNamestring— Middle name
nameSuffixstring— Name suffix (e.g. Jr, Sr, III)
informalNamestring— Informal name / nickname
socialSecuritystring— Social security number
driverLicensestring— Driver license number
maritalStatusstring— Marital status
birthdatestring(date)— Date of birth as an ISO 8601 date (YYYY-MM-DD)(pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$)
employerstring— Employer or organization name
occupationstring— Occupation or job role
citizenshipstring— Citizenship
genderstring— Gender
timezonestring— Timezone identifier as stored by Lawmatics
hobbiesstring— Free-text hobbies or interests
biostring— Free-text biography or notes about the contact
titlestring— Job title
notesarray— Notes to create inline with the contact (write-only; not returned)
[]object
namestringrequired— Note title
bodystringrequired— Note content
customFieldsarray— Custom field values to set on the contact
[]object
idstringnumberrequired— Custom field ID (the API returns it as a number; either a string or number is accepted)
valuestringnumberbooleannullrequired— Value to set (matches the field's type); pass null to clear the field

Tool Output

idstringrequired— Lawmatics contact ID of the newly created contact
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
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 Create Contact tool do?

This page documents the Create Contact tool (lawmatics_create-contact). Create a contact in Lawmatics. The response echoes 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