Law.AI — Lawyer Search
Run Law.AI lawyer search locally via npm stdio or the hosted remote when integrating US attorney discovery into your agent or backend.
Overview
ai.law/lawyer-search is a MCP server for the Build phase that provides verified US lawyer search via npm stdio or hosted HTTP for AI agents.
What is this MCP server?
- Same 991K+ verified US lawyer and attorney search scope as Law.AI’s hosted offering
- npm package lawai-mcp-server with stdio transport for local Claude/Cursor-style setups
- Optional streamable-http remote at https://mcp.law.ai for zero-local-server workflows
- Registry versions 0.2.1 (npm) / 0.2.2 (server metadata) from risk-ai/lawai-mcp-server
- Dual transport choice: self-hosted stdio vs managed HTTP remote
- 991K+ US profiles stated in description
- npm identifier: lawai-mcp-server (registryType npm, transport stdio)
- Remote: https://mcp.law.ai; repository github.com/risk-ai/lawai-mcp-server
What problem does it solve?
Agents cannot help you design legal products with realistic attorney data unless you install or connect a maintained lawyer-search MCP server.
Who is it for?
Developers who want either local stdio MCP (npm) or hosted Law.AI remote while building US-focused legal or referral products.
Skip if: Builders outside the US attorney use case or teams unwilling to run npm MCP processes or call external law.ai infrastructure.
What do I get? / Deliverables
You can run lawai-mcp-server locally or attach the remote so tool calls return searchable attorney matches during integration and feature work.
- Running local Law.AI MCP server process or connected remote endpoint
- MCP tool access to US lawyer search and matching flows
- Reusable integration pattern for legal SaaS and agent demos
Recommended MCP Servers
Journey fit
Attorney search is wired into applications during the build phase as an MCP tool provider, regardless of stdio or HTTP transport. Classified under integrations because this package is the npm-distributable MCP server (lawai-mcp-server) plus the same remote capability as the law.ai catalog.
How it compares
Dual-transport legal directory MCP, not a code-review or deployment skill.
Common Questions / FAQ
Who is ai.law/lawyer-search for?
Solo builders and small teams integrating US lawyer lookup into MCP-enabled coding agents, with a choice of local npm stdio or cloud remote.
When should I use ai.law/lawyer-search?
During build and integrations when you need attorney discovery in the agent loop—especially if you want the npm stdio server for local dev or CI.
How do I add ai.law/lawyer-search to my agent?
Either install/configure the npm package lawai-mcp-server with stdio transport in your MCP client, or add the remote https://mcp.law.ai as streamable-http per your host’s MCP settings.