Skip to main content
Back to Docs

Connect ElevenFlo for AI

Bring ElevenFlo's court-grounded Chapter 11 research graph into Claude, ChatGPT, Cursor, Codex, and other AI clients, with filings, docket events, hearings, and capital structure available inside your workflow.

MCP server URL

https://elevenflo.com/mcp

Remote MCP over HTTP / Streamable HTTP. Use OAuth sign-in only. Do not manually paste a bearer token, API token, or custom Authorization header for ElevenFlo MCP.

Works with

Works with supported remote-MCP clients that support HTTP / Streamable HTTP and OAuth. Local-stdio-only, SSE-only, and manually configured bearer-token setups are not supported for customer MCP access.

On this page

Launch access

Connect in 3 steps

This setup is for accounts with MCP access enabled. If your account is not enabled yet, ask your ElevenFlo contact to turn on launch access before configuring a client.

  1. 01

    Choose your client

    Start with the client you already use. Cursor and VS Code can pre-fill the server; Claude, Codex, and ChatGPT use the same endpoint.

  2. 02

    Authorize access

    The client opens ElevenFlo sign-in and OAuth consent. Do not manually paste a bearer token, API token, or custom Authorization header.

  3. 03

    Run the FTX test

    A successful connection returns FTX Trading Ltd. with case_watch_id 1857, proving the client can reach ElevenFlo tools.

#Quickstart

#1. Confirm access

You need:

  • an ElevenFlo account
  • MCP access enabled for your account or organization
  • an MCP-compatible client
  • browser access for sign-in and consent

If MCP is not enabled yet, ask your ElevenFlo contact to enable launch access before configuring a client.

#2. Add the endpoint

Transport: Remote MCP over HTTP / Streamable HTTP. Clients label this differently — Claude Code uses --transport http, VS Code uses "type": "http", ChatGPT calls it "streaming HTTP" — but it is the same surface.

Add this MCP server URL in your client:

https://elevenflo.com/mcp

Use this name if your client asks for a server name or label:

elevenflo

Remote MCP over HTTP / Streamable HTTP. Use OAuth sign-in only. Do not manually paste a bearer token, API token, or custom Authorization header for ElevenFlo MCP.

#3. Sign in

Start a tool call from your MCP client. The client should open ElevenFlo sign-in and consent.

Approve access only for the client and account you recognize.

#4. Run a smoke test

Ask:

Use ElevenFlo MCP to find the Chapter 11 case for FTX and return the top match with the case name and case_watch_id.

case_watch_id is ElevenFlo's stable internal case identifier. Use it to scope follow-up MCP calls to the same case.

Expected result:

FTX Trading Ltd.
case_watch_id: 1857

#5. Try a research prompt

Find recent filings in the case, identify the plan or disclosure statement, and summarize the key recovery terms using source-backed citations.

#Guardrails

  • Use /mcp as the endpoint path.
  • Reconnect through OAuth if access was revoked or the grant expired.
  • Revoke unused client grants from Account -> AI Tool Connections.
  • Use read_text for exact filing language.
  • Use analyze_document only after selecting relevant documents and chunks.

Client setup

Pick your AI client. Each tab has the install steps and a smoke test. Deep-links pre-fill the MCP server where supported.

Run this from any directory:

claude mcp add --transport http elevenflo https://elevenflo.com/mcp

Then start a prompt that needs ElevenFlo data. Claude Code opens the ElevenFlo OAuth sign-in and consent flow in your browser.

Smoke test:

Use the elevenflo MCP tool search_cases to find the Chapter 11 case FTX and return the top match.

#Troubleshooting

#The client does not open sign-in

Confirm the MCP URL is:

https://elevenflo.com/mcp

Remove any manual Authorization header or static bearer-token setting.

Restart the client and try the FTX smoke test again.

#Sign-in works but the tool call fails

The OAuth grant may have expired, been revoked, or been created for a different endpoint.

Reconnect the elevenflo MCP server and complete sign-in and consent again.

Use:

https://elevenflo.com/mcp

#The client says unauthorized or 401

Likely causes:

  • OAuth was not completed.
  • The grant was revoked.
  • The client is using credentials created for a different endpoint.
  • A stale manual Authorization header is still configured.

Fix:

  • Remove manual headers.
  • Reconnect through OAuth.
  • Retry the FTX smoke test.

#The tool list is missing expected tools

ElevenFlo MCP advertises only the launch subset to enabled accounts. If a tool from the catalog isn't showing up:

  • Check the Tool catalog — that page is the canonical list.
  • Confirm your MCP access; some tools may be gated by entitlement and only appear once your organization is enabled.
  • Reconnect through OAuth if the client cached an older tools/list response.

build_case_context_pack, search_intel_events, lookup_case_law, and generate_bankruptcy_document are not part of the customer launch subset.

If the tool is in the catalog and you have MCP access but the client still does not list it, contact ElevenFlo support with:

  • client name and version
  • endpoint URL
  • account email
  • approximate time of the failed connection

#Search results are empty

Try:

  • checking the case name
  • using search_cases first
  • narrowing by case_watch_id
  • broadening date filters
  • searching summaries before full text
  • using exact phrases only when the phrase is likely to appear in the filing

#Analysis fails on a long document

Use search_within first, then pass selected chunk IDs to analyze_document.

For exact language, use read_text.

#Rate limit or usage error

Check the Account -> AI Tool Connections usage meter. MCP usage is credit-based and resets on the calendar month in UTC. The default launch allowance is 2,500 monthly credits, but account-specific commercial or customer-success exceptions may be applied by ElevenFlo support.

The credit cap is connector-wide. Lightweight lookup and retrieval tools use fewer credits, but they still count against the monthly balance. Current public tool costs are:

ToolCredits
search1
search_cases1
browse_docket1
fetch2
search_content2
get_document_summary2
search_summaries2
search_within3
read_text3
explore_document_graph5
analyze_document15

If the account has credits remaining and the client still reports a usage error, reconnect through OAuth and retry. If the error persists, contact ElevenFlo support. Include the client name, account email, endpoint, tool name, and approximate time.

#Unsupported client

Use a client that supports hosted remote MCP over HTTP with OAuth.

If your client only supports local stdio MCP servers or manual bearer tokens, it is not a supported customer path for ElevenFlo MCP.

#Support

For MCP support, contact your ElevenFlo representative.

Copy this block, fill it in, and paste it into your support message:

Organization:
Account email:
MCP client and version:
Endpoint URL:
Tool or prompt attempted:
Approximate time:
Error message:
Affects one user or multiple users:

#Severity

Access blocked

Use when no authorized user in your organization can connect.

Research blocked

Use when the client connects but core read tools fail.

Incorrect or missing data

Use when a case, filing, summary, or source result appears wrong or incomplete.

Client setup help

Use when a supported client cannot complete OAuth or cannot find the elevenflo server.

#Before contacting support

Run the smoke test:

Use ElevenFlo MCP to find the Chapter 11 case for FTX and return the top match with the case name and case_watch_id.

Expected:

FTX Trading Ltd.
case_watch_id: 1857

If the smoke test fails, include the failure text in the support request.