ElevenFlo MCP is a hosted remote MCP server for court-grounded Chapter 11 bankruptcy and restructuring research.
Production endpoint:
https://elevenflo.com/mcp
Transport: remote MCP over HTTP / Streamable HTTP.
Authentication: ElevenFlo web-app sign-in, OAuth 2.1, PKCE, and explicit consent. Do not configure static bearer tokens or pasted API keys for ElevenFlo MCP.
ElevenFlo MCP is included with the ElevenFlo Pro plan and provisioned automatically — see Access.
These pages mirror the live docs at https://elevenflo.com/docs and are published from the ElevenFlo monorepo. Do not edit them here.
Client setup:
Workflow recipes:
- Overview
- Daily case brief
- First-day filings triage
- DIP and cash-collateral terms
- Scheduling and notifications
- Skill files
- Safety and verification
The official MCP Registry metadata lives in server.json.
- Registry name:
com.elevenflo/mcp - Display title:
ElevenFlo MCP - Transport:
streamable-http - Remote URL:
https://elevenflo.com/mcp - Namespace authentication: domain-based authentication for
elevenflo.com
OpenAI/ChatGPT public app review is a separate platform review path and is not controlled by this registry metadata.
Unauthenticated browser requests to https://elevenflo.com/mcp may return
401. That path is the protected MCP protocol endpoint, not a browser
documentation page.
The tool set is read-only, OAuth-only, and source-grounded. It supports
Chapter 11 case lookup, docket browsing, filing and source discovery, hearing
transcript search where indexed, exact court-document text retrieval, filing
summaries, targeted filing analysis, document relationship exploration, and
OpenAI-compatible search/fetch.
The tool set does not support filing documents, sending email, modifying dockets, creating legal-document artifacts, changing account settings, managing billing, or granting access to other users.
The tool catalog is the canonical list of what the connector exposes.
This repository contains public setup docs, workflow recipes, tool catalog
copy, changelog, llms.txt, and registry metadata.
It does not contain ElevenFlo backend source, ingestion or ranking logic, private schemas, customer identifiers, secrets, billing internals, or provider integrations.