LegalSearch

What LegalSearch MCP server does

LegalSearch MCP server gives external agents access to Roop’s public Indian legal corpus through the Model Context Protocol. Its coverage includes public judgments, statutes, and subordinate legislation. The repository is intended for agents that already support MCP and need a vendor-neutral way to ground research responses in that public material.

The service is deliberately narrower than a complete legal-work platform. It does not expose private workspaces, matters, documents, drafts, user data, internal Roop systems, privileged tools, or non-public operational details. It also does not provide legal advice.

How it works

An MCP-capable agent connects to Roop’s public remote endpoint at https://mcp.roopslaw.ai/mcp. The agent can then request searches and bounded result packets from the public judgment and legislation corpus. A separate corpus-status capability provides information about the state of the public corpus.

The repository includes a master prompt and legal-grounding guidance for configuring agent behavior. These materials are intended to help agents use retrieved legal content appropriately, preserve grounding, and direct users to verify legal work against official sources. The service can be used without migrating an existing agent stack to the wider Roop platform.

The repository also publishes supporting endpoints: /health for service health, a discovery document at /.well-known/roop-public-mcp.json, and links to Roop’s bot guide and llms.txt resource.

Setup and configuration

Start by providing the repository’s master prompt to the agent, then follow the direct MCP instructions in docs/mcp-setup.md. Configuration depends on the MCP-capable client being used. The README names Gemini agents, Codex, Claude Code, Hermes, OpenClaw-style agents, Cursor, and VS Code agent mode as supported use contexts, along with other MCP-capable tools.

The public endpoint is available for MCP connections. Authenticated access may use a local ROOP_PUBLIC_MCP_API_KEY environment variable. API keys should not be committed to source control. The repository’s security guidance should be consulted when configuring credentials.

Tools and capabilities

LegalSearch MCP server exposes these documented capability areas:

• Search across public Indian judgments.
• Retrieve bounded judgment packets.
• Search public statutes and subordinate legislation.
• Retrieve bounded statute and subordinate-legislation packets.
• Check public corpus status.

The material provided does not specify individual tool names, request schemas, response fields, ranking behavior, or pagination controls, so those details should be obtained from the MCP discovery and setup resources rather than assumed by a client implementation.

Limitations and notes

Access is limited to Roop’s public corpus. The service does not provide private or matter-specific data, drafts, internal systems, secrets, or privileged tools. Retrieved material is intended for research grounding, not as a substitute for legal advice. Users should verify legal work against official sources and consult a qualified professional when appropriate.

The service is positioned as an interoperability layer rather than the full Roop platform. The README states that sustained legal work may require platform features such as research, drafting, matter context, verification, collaboration, and billing, but those capabilities are not provided by this public MCP service.