lawruler-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LAWRULER_API_KEY | Yes | Your LawRuler API key | |
| LAWRULER_BASE_URL | Yes | The base URL of the LawRuler instance (e.g., https://yourfirm.lawruler.com) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_leadB | Create a new lead/intake. FirstName+LastName or FullName required. CellPhone and Email strongly recommended. |
| create_lead_fullC | Create a new lead/intake with full field set including address, DOB, and contact preferences. |
| create_lead_oboA | Create a lead with duplicate checking disabled (for On-Behalf-Of cases where the same contact has multiple matters). |
| get_leadA | Retrieve a lead/intake by LeadID. Returns contact info, status, case type, and all stored fields. |
| update_lead_statusC | Update the status of a lead/intake. Common values: New Lead, Emailed Intake Questionnaire, Sent Retainer Contract, Signed Retainer Contract, Converted to Case, Approved. |
| update_lead_assigneeC | Assign a lead/intake to a staff member (LeadAssignee — the user managing the lead). |
| update_lead_ownerB | Set the owner of a lead/intake (LeadOwner — the attorney or partner who owns the matter). |
| update_lead_case_typeB | Update the case type of a lead/intake (e.g., Auto Accident, Workers Compensation, Divorce). |
| update_lead_summaryC | Update the case description/summary for a lead. |
| add_conversation_noteB | Add a conversation note or chat transcript to a lead. |
| add_tags_to_leadA | Add tags to a lead. For multiple tags, separate with commas: 'New, Level 1, High Value'. |
| update_lead_languageB | Update the preferred language for a lead (e.g., Spanish, French, Mandarin). |
| update_lead_contact_infoB | Update contact information fields on a lead (phone, email, address). |
| set_custom_fieldA | Set a custom field on a lead. field_name is the API parameter name (e.g., custom2413). Custom field names are found in the LawRuler Intake Form Builder. |
| update_lead_fieldsC | Update multiple fields on an existing lead at once. custom_fields_json accepts a JSON object of field_name:value pairs for custom fields. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/RosenAdvertising/lawruler-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server