folio-mcp

Purpose: Providing a standards-based server for federated legal information using the Model Context Protocol.

Inferred · not functionally tested

Audience: Legal tech developers and researchers

Inferred · not functionally tested

Functions: Unknown

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI, WEB · deployment: browser, cli, api_only, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: folio.openlegalstandard.org · github.com. These links do not verify the individual claims.

In the Frameworks & SDKs space, folio-mcp takes a focused approach. Inferred · not functionally tested: It focuses on providing a standards-based server for federated legal information using the Model Context Protocol. Inferred · not functionally tested: It is built as an open-source project for legal tech developers and researchers. Basis unknown · not verified: folio-mcp is open source under the MIT license. Basis unknown · not verified: It ships for the web, the command line, and API, and it can be self-hosted.

Behind folio-mcp is Alea Institute, and it first shipped in 2026. Development happens publicly on GitHub with 3 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include MCP server, ontology support, and federated legal data. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.