Available on every plan
Connect in 3 steps
ElevenFlo MCP is available on every plan — free accounts include 2,500 credits a month, Pro includes 100,000, and there is no separate access request. Sign in with your ElevenFlo account when your client prompts for OAuth.
- 01
Choose your client
ChatGPT users should start from the published app directory. Cursor and VS Code can pre-fill the endpoint; Claude, Codex, and private/workspace ChatGPT Developer Mode use it directly.
- 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.
- 03
Run the FTX test
A successful connection returns FTX Trading Ltd. with case_id 1857, proving the client can reach ElevenFlo tools.
#Quickstart
Setup takes about 5 minutes with any ElevenFlo account.
#1. Confirm access
You need:
- an ElevenFlo account with a verified email address (MCP is available on every plan — free accounts include 2,500 credits per month, Pro includes 100,000)
- an MCP-compatible client
- browser access for sign-in and consent
MCP is provisioned automatically — there is no separate access request. If a tool call returns an access error, confirm your email address is verified.
#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", and private/workspace ChatGPT Developer Mode calls it "streaming HTTP" — but it is the same surface.
ChatGPT users should start with the published app directory unless using private/workspace Developer Mode.
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
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 FTX Trading Ltd. Chapter 11 case. Return the top match with case name, court, case number, and case identifier.
case_id is the stable case identifier returned by ElevenFlo MCP. The response also includes case_watch_id, the legacy name for the same value; use either identifier in follow-up MCP calls.
Expected result:
FTX Trading Ltd.
case_id: 1857
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. - Each OAuth approval creates an independent client grant.
- Access tokens refresh automatically. The default refresh-token family lifetime is 30 days from OAuth approval; daily reauthorization is not expected.
- Reconnect through OAuth if access was revoked, entitlement changed, or the grant expired after its refresh-token family lifetime.
- Revoke unused client grants from Account → MCP connections.
- 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. ChatGPT starts with the published app directory; deep-links pre-fill the MCP server where supported.
Run this from any directory:
claude mcp add --scope user --transport http elevenflo https://elevenflo.com/mcp
claude mcp login elevenflo
claude mcp get elevenflo
Then start a prompt that needs ElevenFlo data. If OAuth has expired, Claude Code opens the ElevenFlo sign-in and consent flow in your browser.
Smoke test:
Use ElevenFlo MCP to find the FTX Trading Ltd. Chapter 11 case. Return the top match with case name, court, case number, and case identifier.
For Claude Code skill-file packaging, see Skill files.
#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.
Authorizing the same ElevenFlo account from another compatible client should not revoke this connection. Access tokens refresh automatically, and the default refresh-token family lifetime is 30 days from OAuth approval; daily reauthorization is not expected. Reauthorization is expected after the grant is revoked, entitlement changes remove access, or the refresh-token family reaches its absolute lifetime.
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.
- The client failed to persist a rotated refresh token and is replaying stale local credentials.
- 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
ElevenFlo MCP advertises only its research tool set. If a tool from the catalog isn't showing up:
- Check the Tool catalog — that page is the canonical list.
- Confirm your email address is verified. The same tool set is available on every plan.
- Reconnect through OAuth if the client cached an older
tools/listresponse.
build_case_context_pack, search_intel_events, lookup_case_law, and
generate_bankruptcy_document are not part of the current customer tool set.
If the tool is in the catalog and 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_casesfirst - narrowing by
case_idorcase_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 → MCP connections usage meter for your current allowance and remaining balance. MCP usage is credit-based and resets at the start of each calendar month.
The credit cap is connector-wide. Lightweight lookup and retrieval tools use fewer credits than document-analysis tools, but they still count against the monthly balance.
Free accounts include 2,500 credits per month. If a tool call reports the credit limit was reached, the balance resets at the start of the next calendar month, or upgrade to Pro for 100,000 credits per month.
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, email support@elevenflo.com.
Copy this block, fill it in, and include it in your message:
Organization:
Account email:
MCP client and version:
Endpoint URL:
Case or filing involved:
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 FTX Trading Ltd. Chapter 11 case. Return the top match with case name, court, case number, and case identifier.
Expected:
FTX Trading Ltd.
case_id: 1857
case_watch_id: 1857
If the smoke test fails, include the failure text in the support request.