On this page
Controlled beta
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 the customer beta before configuring a client.
- 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.
- 02
Authorize access
The client opens ElevenFlo sign-in and OAuth consent. Do not paste a bearer token or custom authorization header.
- 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 the customer beta before configuring a client.
#2. Add the endpoint
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
Do not add a manual Authorization header. Use the OAuth flow in the client.
#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.
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
/mcpas the endpoint path. - Reconnect through OAuth if access was revoked or the grant expired.
- Use
read_textfor exact filing language. - Use
analyze_documentonly 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
Authorizationheader is still configured.
Fix:
- Remove manual headers.
- Reconnect through OAuth.
- Retry the FTX smoke test.
#The tool list is missing expected tools
The customer beta exposes the launch subset only.
generate_bankruptcy_document is not part of the customer launch subset.
If a read-oriented tool is missing, 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_casesfirst - 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
Retry later or contact ElevenFlo support. Include the client name, account email, endpoint, 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 beta support, contact your ElevenFlo representative.
Include:
- organization name
- account email
- MCP client and version
- endpoint URL
- tool or prompt attempted
- approximate time
- error message
- whether the issue 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.