CourtAPI — Federal Court Data vs Firecrawl MCP Server
A side-by-side look at the CourtAPI — Federal Court Data and Firecrawl MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose CourtAPI — Federal Court Data for legal work as a local process; choose Firecrawl MCP Server for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose CourtAPI — Federal Court Data when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
COURTAPI_APP_ID, COURTAPI_APP_KEY, COURTAPI_BASE_URL. - You want tools like
find_cases, get_case, get_dockets.
Choose Firecrawl MCP Server when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
FIRECRAWL_API_KEY, HTTP_STREAMABLE_SERVER. - You want tools like
firecrawl_scrape, firecrawl_map, firecrawl_search.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Search & Data Extraction |
| Quality signal | 56/100 · Good | 90/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | COURTAPI_APP_IDCOURTAPI_APP_KEYCOURTAPI_BASE_URL | FIRECRAWL_API_KEYHTTP_STREAMABLE_SERVER |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 7,669 |
| Directory activity | 3 views 0 installs 0 upvotes | 13 views 0 installs 0 upvotes |
| Tools | 10 | 25 |
| Full listing | View CourtAPI — Federal Court Data | View Firecrawl MCP Server |
Tools & capabilities
CourtAPI — Federal Court Data tools 10
find_casesDiscover federal court cases you don't have the court+number for yet. Pass a party/company name, a (partial) case number, or free-text keywords. Returns court_code + case_number needed by all other tools. No PACER cost. Note: keyword search (search-filings) charges 1 CourtAPI API call per 25 results returned. Examples: query='Sbarro', query='1:14-bk', query='retail chapter 11 2026'.get_caseGet all metadata for a known case: title, chapter, judge, key dates (filed/closed/discharged), assets, liabilities, and links to sub-resources (dockets, claims, parties, etc.) with their last-modified timestamps. Always call this first after finding a case. The response includes a 'menu' object where each entry has a 'modified' timestamp (null = never purchased) showing what sub-resources are available. Free unless include_live_pacer=true.get_docketsGet the docket sheet for a case — all filings in chronological order with dates, descriptions, and attached document info (is_cached, download_cost). The header includes judge, attorneys, trustees, and 341 meeting date. Supports keyword search and date/number range filtering. Free unless include_live_pacer=true.get_documentGet a PDF attached to a docket entry. Always checks the cache first. If cached (is_cached=true), returns download_url + preview_url + ocr_link at no cost. If not cached and purchase=true, buys from PACER and returns download_url + receipt. If not cached and purchase=false (default), returns cost info so you can decide. docket_seq comes from docket entries (e.g. '42.00000'). part defaults to 1 (main doc).get_claimsGet the bankruptcy claims register — all proofs of claim filed by creditors, with amounts (filed/allowed/paid), claim type (secured/unsecured), creditor names, and filing dates. Essential for Chapter 11 analysis and creditor research. Supports keyword search and date/number range filtering.get_partiesGet all parties in a case (debtors, creditors, plaintiffs, defendants, trustees) and optionally their attorneys with firm name, contact info, and bar number. Useful for conflicts checks, service lists, and identifying who is involved.get_creditorsGet the creditor list for a bankruptcy case — all creditors scheduled in Schedules D/E/F, whether or not they filed a proof of claim. Different from get_claims (which shows filed proofs of claim).ncl_searchSearch PACER's National Case Locator across all federal courts at once. More comprehensive than find_cases for party name searches — queries PACER directly. Costs PACER credits. Returns up to ~50 cases per page; pass search_id + page to paginate. Use for: finding a person's cases across all courts, SSN lookups, cross-court party searches.list_courtsList all PACER courts with their court codes. Call this when you need a court_code and don't know it. Returns ~200 courts; use type to filter. Common codes: nysbke, debke, ilnbke, cacdbe, txnbke.get_pacer_credentialsCheck or update PACER credentials stored in CourtAPI. PACER credentials are required before any include_live_pacer=true call. action='check' → show stored username (password not returned). action='set' → store pacer_user + pacer_pass. action='validate' → test credentials without storing. action='delete' → remove stored credentials.
Firecrawl MCP Server tools 25
firecrawl_scrapeRetrieve and extract content from one supplied URL through Firecrawl. Use this when the request identifies a page and needs its content or defined fields. It can return markdown, HTML, links, screenshots, branding data, a targeted answer, or JSON matching a supplied schema; JSON is useful when the requested result has defined fields, while markdown preserves readable page content. This tool operates on a known page. For a set of pages use `firecrawl_crawl`, and to discover page URLs use `firecrawl_map` or `firecrawl_search`. Options include JavaScript render delay, cache age, main-content filtering, PII redaction, and lockdown cache-only retrieval. Browser actions may change the live page when interactive actions are enabled. Firecrawl may reuse recently indexed content instead of refetching the page, and the reuse window varies by domain. Set `maxAge: 0` to force a live fetch, or a smaller `maxAge` to bound how stale reused content may be. A successful response does not by itself confirm that the state it describes is still current. Returns the selected content formats and page metadata.firecrawl_mapEnumerate URLs indexed under one website through Firecrawl without fetching each page's content. Use this when the request asks for a site's URL inventory, when several relevant pages must be located, or when the desired page URL is unknown. An optional `search` term narrows the URL list, while sitemap, subdomain, query-parameter, and result-limit options control coverage. Returns matching URLs rather than page bodies. Retrieve one page with `firecrawl_scrape`; collect content across multiple pages with `firecrawl_crawl`.firecrawl_searchSearch web, news, or image sources and return ranked results. Operators include quoted phrases, `-term`, `site:host`, `inurl:term`, `intitle:term`, and `related:host`; the set is non-exhaustive. `includeDomains` and `excludeDomains` are mutually exclusive hostname filters; categories limit results to GitHub, research, PDF, or developer sources. For a programming question, add `categories: ["developer"]`. It searches an index of GitHub issues, merged pull requests, repository READMEs, and curated documentation sites, and returns the hits in `data.developer` beside the web results. `categories: ["research"]` restricts these web results to research-affiliated websites and returns page snippets. The `firecrawl_research_*` tools are a separate surface that searches paper abstracts and full text across biomedical (PubMed, bioRxiv, medRxiv) and arXiv literature. `scrapeOptions` can attach extracted page content; pages fetched this way use a fixed reuse window and ignore `maxAge`, so use `firecrawl_scrape` when a live fetch is required. Returns source-type result groups and usage metadata. Authenticated responses can include an `id` for optional search feedback.firecrawl_crawlStart a multi-page crawl at a website URL, poll it to a terminal state, and return the final status and collected data. Scope can be bounded with include/exclude paths, depth, page limit, subdomain/external-link controls, sitemap handling, delay, and scrape options. Crawl results can be large; use conservative limits when full-site coverage is unnecessary. Webhooks and interactive scrape actions are unavailable in safe mode. Returns the crawl ID, status, and page data.firecrawl_check_crawl_statusRetrieve the current status, progress, and available results for an existing crawl ID. This only reads Firecrawl job state and does not start or modify the crawl.firecrawl_extractDeprecated compatibility entry point. Use firecrawl_scrape once per known URL with formats: ["json"] and jsonOptions containing the prompt and schema. Use firecrawl_search or firecrawl_agent before Scrape when URLs are not known.firecrawl_agentStart an asynchronous web research job from a prompt, optional seed URLs, and an optional JSON schema. Use this for a requested synthesis across multiple sources when the task can wait for asynchronous completion. The agent can search, navigate, read pages, and assemble a structured result. This call returns only a job ID, not the research result. Read the job with `firecrawl_agent_status` until it reaches `completed` or `failed`; research commonly takes several minutes. If the job cannot finish within the task's available time, `firecrawl_search` and `firecrawl_scrape` can gather evidence synchronously.firecrawl_agent_statusRetrieve progress or final results for a `firecrawl_agent` job ID. A `processing` response is non-terminal and does not contain the final research result. Check again after 15–30 seconds until the status is `completed` or `failed`; complex jobs can take several minutes. If the job cannot finish within the task's available time, use `firecrawl_search` and `firecrawl_scrape` to complete the requested output. Returns job status, progress information, and result data when completed.firecrawl_interactOpen or reuse a live browser session to navigate a page, click controls, fill fields, or run browser code. Provide either `url` or `scrapeId`, and either a natural-language `prompt` or executable `code`; code can run as Bash, Python, or Node with a bounded timeout. This acts on the live site, so actions such as form submission can create persistent external side effects. Returns execution output, stdout/stderr, exit status, and session viewing URLs.firecrawl_interact_stopStop the live interact session associated with a `scrapeId` and release its resources. Returns a success confirmation.firecrawl_parseParse one supported document into markdown, HTML, links, summary, targeted answers, or JSON matching a schema. Supported inputs include common HTML, PDF, Word, RTF, OpenDocument, and spreadsheet files; PDF parsing can be bounded with `pdfOptions.maxPages`. Local MCP reads `filePath` from the server filesystem. Hosted MCP uses two calls: first provide `filePath` to receive upload instructions, upload locally, then call again with the returned `uploadRef`; do not send both fields together. Remote web URLs belong in `firecrawl_scrape`. Set `redactPII` to request redaction of personally identifiable information in the returned content. `zeroDataRetention` requires an eligible authenticated account; omit it for anonymous keyless use. Returns upload instructions for hosted phase one or parsed document content for the final call.firecrawl_monitor_createCreate a recurring scrape, crawl, or search monitor that compares each check with its retained predecessor. The simple form accepts `page`/`pages` or `queries` plus a plain-language `goal`; the advanced `body` form controls targets, schedule, change-tracking formats, judging, retention, webhook, and notifications. In the simple form, a `goal` is required. If `queries` contains one or more non-empty values and is supplied with `page`/`pages`, `queries` create the search target and page targets are ignored. A monitor schedules future network checks and can send configured email or webhook notifications. Returns the created monitor.- +13 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
CourtAPI — Federal Court Data
{
"mcpServers": {
"courtapi-federal-court-data": {
"command": "npx",
"args": [
"-y",
"@courtio/courtapi-mcp"
],
"env": {
"COURTAPI_APP_ID": "YOUR_COURTAPI_APP_ID_HERE",
"COURTAPI_APP_KEY": "YOUR_COURTAPI_APP_KEY_HERE",
"COURTAPI_BASE_URL": "YOUR_COURTAPI_BASE_URL_HERE"
}
}
}
}
Firecrawl MCP Server
{
"mcpServers": {
"firecrawl-firecrawl-mcp-server": {
"command": "npx",
"args": [
"-y",
"firecrawl-mcp"
],
"env": {
"FIRECRAWL_API_KEY": "YOUR_FIRECRAWL_API_KEY_HERE",
"HTTP_STREAMABLE_SERVER": "YOUR_HTTP_STREAMABLE_SERVER_HERE"
}
}
}
}
Frequently asked questions
CourtAPI — Federal Court Data is categorized under Legal and uses a local stdio subprocess. Firecrawl MCP Server belongs to Search & Data Extraction and uses a local stdio subprocess. Pick CourtAPI — Federal Court Data for legal work and Firecrawl MCP Server for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
CourtAPI — Federal Court Data has no declared pricing — check the project's own site. Firecrawl MCP Server is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add courtapi-federal-court-data and firecrawl-firecrawl-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CourtAPI — Federal Court Data has a quality signal of 56/100 (Good) with 3 views, 0 installs and 0 GitHub stars. Firecrawl MCP Server has 90/100 (Excellent) with 13 views, 0 installs and 7,669 GitHub stars.