IDE-native workflow
Connect once from your MCP client configuration. Lawcel tools appear alongside other MCP capabilities in supported editors.
Platform · MCP server
Not every compliance question waits for a pull request. The MCP server brings Lawcel analysis into the tools developers already use while writing code.
Connect once from your MCP client configuration. Lawcel tools appear alongside other MCP capabilities in supported editors.
Submit a title, description, and optional diff for the same classification pipeline used by webhook-driven integrations.
List up to 50 recent compliance cases and all org documents from your workspace without switching to the dashboard.
MCP uses the same prefixed API keys managed in Lawcel settings. Revoke a key and IDE access stops immediately.
The MCP server lives in the Lawcel repository as a Node.js package with stdio transport - no separate hosted service to provision.
MCP is ideal for pre-PR checks and exploratory analysis. Connected GitHub, Linear, and Jira integrations remain the primary continuous monitoring path.
Setup
Webhook integrations catch changes as they move through your toolchain. MCP fills the gap when a developer wants to sanity-check a local diff or spike before opening a ticket.
Setup instructions and copy-ready config live under Connections → MCP in the Lawcel dashboard.
Create an API key
Generate a key under Connections → API. Starter includes one key; Pro includes unlimited keys. MCP uses the same keys as the REST API.
Configure your IDE
Add the Lawcel MCP server to your client config using the documented command and environment variables.
Analyze before you push
Run analysis on work-in-progress to surface likely document impacts early - then let webhooks handle continuous monitoring after push.
Wire Lawcel into your stack - or start with a free scan of your public legal pages.