Know what your firm knows — instantly

Discover what your firm can achieve when every lawyer has instant access to your full institutional knowledge.

DeepJudge MCP

The DeepJudge connector brings your organization's legal knowledge base into Claude using the Model Context Protocol (MCP). Search, retrieve, and analyze your firm's documents and matter data directly inside a Claude conversation — grounded in your own work product.

Access is user-scoped: the connector only ever surfaces content your DeepJudge account is already authorized to see.

Overview

With the DeepJudge connector, you can:

  • Find prior work product and precedent — surface relevant past matters, templates, and "have we done this before?" answers grounded in your firm's own documents.
  • Search in natural language — query your firm's entire corpus (DMS, SharePoint, intranet, matter systems) by intent, not just keywords.
  • Trust the results — permission-aware retrieval respects your existing access controls and ethical walls, so you only see what you're entitled to view.
  • Run knowledge-grounded workflows — support tasks like RFP responses, clause comparisons, and matter summaries on top of your indexed firm knowledge.
  • Benchmark negotiations — draw on previously negotiated documents to respond to and benchmark opposing counsel positions.

Requirements

  • An active DeepJudge account with MCP access enabled on your account.
  • Your organisation's MCP server URL — provided by your DeepJudge administrator.
  • Access to claude.ai.

If you're unsure whether MCP access is enabled for you, contact your DeepJudge administrator.

Setup Guides

Claude

  1. Sign in to claude.ai.
  2. Open your profile menu and go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the MCP server URL provided by your administrator.
  5. Click Connect and sign in with your normal DeepJudge credentials when prompted.

The connector becomes available in your Claude conversations immediately after sign-in. You do not need a separate password — your existing DeepJudge login is used.

Your MCP server URL is specific to your organisation. There is no public endpoint. If you do not have a URL, contact your DeepJudge administrator.

Limitations

  • The connector can only access content your DeepJudge account is permitted to see. Permissions are not elevated through MCP.
  • Results depend on what has been indexed in your DeepJudge deployment. Content not ingested into DeepJudge is not accessible through the connector.
  • The connector requires an active DeepJudge session. If your session expires, Claude will prompt you to sign in again.

Support

For access and configuration questions, contact your DeepJudge administrator.

For product support, reach out to support@deepjudge.ai.

‍