LegalContext

Created By
protomateda year ago
LegalContext is an open-source Model Context Protocol (MCP) server that creates a secure, standardized bridge between law firms' document management systems (specifically Clio) and AI assistants (starting with Claude Desktop)
Overview

What is LegalContext?

LegalContext is an open-source Model Context Protocol (MCP) server that creates a secure, standardized bridge between law firms' document management systems (specifically Clio) and AI assistants (starting with Claude Desktop). It enables AI tools to access, retrieve, and incorporate firm document context while maintaining complete security and control over sensitive information.

How to use LegalContext?

To use LegalContext, clone the repository, install the dependencies, build the project, and start the server. You can also test the MCP server using the included test client.

Key features of LegalContext?

  • Secure integration with Clio document management system.
  • Modular architecture built on NestJS.
  • Local document processing with zero data transmission to external servers.
  • Comprehensive testing infrastructure.

Use cases of LegalContext?

  1. Integrating AI assistants with law firm document management systems.
  2. Enhancing document retrieval and processing capabilities in legal tech.
  3. Ensuring secure handling of sensitive legal documents.

FAQ from LegalContext?

  • Is LegalContext secure?

Yes! LegalContext prioritizes security by keeping all document processing local and using secure transport methods.

  • Can I contribute to LegalContext?

Yes! Contributions are welcome, and guidelines can be found in the repository.

  • What is the license for LegalContext?

LegalContext is licensed under the Mozilla Public License 2.0.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
protomated
Star
2
Language
TypeScript
License
MPL-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago