Productivity · Local MCP server
Lawmatics MCP
Connect Claude to Lawmatics: matters, contacts, pipelines, tasks, forms, custom fields, invoices.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.oktopeak/lawmatics-mcp- Version
- 1.0.0
- Status
- Active
- Category
- productivity
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-08
- Updated
- 2026-08-08
- Publisher
- oktopeak (GitHub) · 5 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/oktopeak) · how
- Repository
- github.com/oktopeak/lawmatics-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @oktopeak/lawmatics-mcp | 1.0.0 | stdio |
How to connect Lawmatics MCP
Lawmatics MCP runs locally from a Node.js package published to the npm registry: @oktopeak/lawmatics-mcp version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @oktopeak/lawmatics-mcp@1.0.0. It reads these environment variables: LAWMATICS_ACCESS_TOKEN (required, secret), LAWMATICS_READ_ONLY, LAWMATICS_EXPERIMENTAL_TOOLS, LAWMATICS_RATE_LIMIT_PER_MIN, LAWMATICS_AUDIT_LOG, LAWMATICS_AUDIT_LOG_PATH, LAWMATICS_CLIENT_ID, LAWMATICS_CLIENT_SECRET (secret), LAWMATICS_REDIRECT_PORT and LAWMATICS_API_BASE; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"lawmatics-mcp": {
"command": "npx",
"args": [
"-y",
"@oktopeak/lawmatics-mcp@1.0.0"
],
"env": {
"LAWMATICS_ACCESS_TOKEN": "<secret>",
"LAWMATICS_READ_ONLY": "<value>",
"LAWMATICS_EXPERIMENTAL_TOOLS": "<value>",
"LAWMATICS_RATE_LIMIT_PER_MIN": "<value>",
"LAWMATICS_AUDIT_LOG": "<value>",
"LAWMATICS_AUDIT_LOG_PATH": "<value>",
"LAWMATICS_CLIENT_ID": "<value>",
"LAWMATICS_CLIENT_SECRET": "<secret>",
"LAWMATICS_REDIRECT_PORT": "<value>",
"LAWMATICS_API_BASE": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from oktopeak (GitHub)
| Server | Runs |
|---|---|
| Clio MCPConnect Claude to Clio: 34 tools for matters, custom fields, notes, documents, folders, billing. | Local · stdio |
| Filevine MCPOpen-source MCP server connecting Claude to Filevine practice management. Built by Oktopeak. | Local · stdio |
| IntakeQ MCPIntakeQ/PracticeQ MCP connector with HIPAA §164.312(b) audit logging on every PHI read/write. | Local · stdio |
| Mycase MCPConnect Claude to MyCase: cases, contacts, documents, tasks, calendar, calls, time, billing, staff. | Local · stdio |
More productivity servers
| Server | Runs |
|---|---|
| LatexPersistent AI LaTeX workspace: edit and compile multi-file projects, export publication-ready PDFs. | Remote · HTTPLive check: sign-in required |
| LatticeNetPublish articles and notes under your own byline, to a readership of other AI agents. | Remote · HTTPLive check: sign-in required |
| LaunchCheck x402Paid x402 MCP tool for stress-testing launch and marketing copy before publication. | Remote · HTTPLive check: ✓ handshake |
| Laver MCPKanban boards, sprints, tickets and a team wiki, with versioned writes for concurrent agents. | Local · stdio |
| LaxisSearch and read your Laxis meeting transcripts, AI summaries, and participants from Claude. | Remote · HTTPLive check: sign-in required |
| LayerCallScore an IP, email, phone, domain or device for fraud in one call, with the signals behind it. | Remote · HTTPLive check: ✓ handshake |
| LayerOne (DocX + Sign)MCP server for LayerOne DocX (documents & Factur-X) and Sign (e-signature) APIs. | Local · stdio |
| Layers Marketing MCPGive your agent marketing superpowers: research, renders, delivery, paid campaigns, measurement. | Remote & Local · HTTP, stdioLive check: sign-in required |