Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SSE_LOCALNoEnables SSE local mode (HTTP stream transport), in which clients should send Authorization: Bearer <fco_access_token> on MCP requests.
CLOUD_SERVICENoWhen true, runs in hosted mode and additionally serves the search-only endpoint.
FIRECRAWL_API_KEYNoYour Firecrawl API key. Required when using cloud API (default). Optional when using self-hosted instance with FIRECRAWL_API_URL.
FIRECRAWL_API_URLNoCustom API endpoint for self-hosted instances. Example: https://firecrawl.your-domain.com. If not provided, the cloud API will be used (requires API key).
FIRECRAWL_OAUTH_TOKENNoA static OAuth access token (fco_...) for stdio transport, used instead of FIRECRAWL_API_KEY. Only access tokens are supported; refresh tokens (fcr_...) must be exchanged at the token endpoint.
HTTP_STREAMABLE_SERVERNoSet to true to run the server using Streamable HTTP locally instead of the default stdio transport. Use the url: http://localhost:3000/mcp
FIRECRAWL_MCP_SEARCH_PORTNoPort for the search-only instance, for isolated tests only. Must not be used independently in the hosted deployment.
FIRECRAWL_MCP_SEARCH_ENABLEDNoOperational toggle for the hosted search-only instance (default true). Set to false to prevent the search instance from starting.
FIRECRAWL_NO_SEARCH_FEEDBACKNoSet to 1 (or FIRECRAWL_DISABLE_SEARCH_FEEDBACK=1) to opt out of the firecrawl_search_feedback tool so it is not registered.
FIRECRAWL_MCP_SEARCH_ENDPOINTNoEndpoint for the search-only instance, for isolated tests only. Must not be used independently in the hosted deployment.
FIRECRAWL_NO_ENDPOINT_FEEDBACKNoSet to 1 (or FIRECRAWL_DISABLE_ENDPOINT_FEEDBACK=1) to opt out of the firecrawl_feedback tool so it is not registered.
FIRECRAWL_DISABLE_SEARCH_FEEDBACKNoSet to 1 to opt out of the firecrawl_search_feedback tool so it is not registered.
FIRECRAWL_MCP_SEARCH_RESOURCE_URLNoOAuth protected-resource identifier for the search-only instance, for isolated tests only. Must not be used independently in the hosted deployment.
FIRECRAWL_DISABLE_ENDPOINT_FEEDBACKNoSet to 1 to opt out of the firecrawl_feedback tool so it is not registered.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
logging
{}
completions
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
firecrawl_scrapeA

Scrape one URL and return its content: markdown by default, or HTML, links, screenshots, branding data, a targeted answer, or JSON matching a supplied schema. Use it when the request identifies a page and needs its content or defined fields. Use firecrawl_search when additional web sources are needed; on an authenticated session, firecrawl_map lists a site's URLs and firecrawl_crawl collects a set of pages.

Firecrawl may serve recently indexed content; set maxAge: 0 for a live fetch or a smaller maxAge to bound staleness. A successful response does not by itself confirm the page is still current. Browser actions can change the live page when interactive actions are enabled. Authenticated responses can include a metadata.scrapeId for optional scrape feedback.

On an authenticated session with Alexandria access, firecrawl_search with sources unset and firecrawl_find_tools can discover providers for the same fields across several pages; a matching provider returns typed records in one call. Keyless sessions have no provider matches.

Alexandria mode, on an authenticated session with Alexandria access: alexandria selects catalogued capability execution and is mutually exclusive with url.

firecrawl_mapA

Enumerate 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. Authenticated responses can include an id for optional map feedback.

firecrawl_searchA

Search web, news, or image sources and return ranked results with query-relevant highlights. Each web result is a title, URL, and description; use firecrawl_scrape on a result URL when the excerpt is not enough.

Authenticated search also returns matching Alexandria data providers in data.tools (companies, people, jobs, finance and filings, public records and government spending, real estate, places and restaurants, retail and prices, package registries and developer data, news, research, and more). Prefer a provider over scraping pages when the task needs the same fields across several entities, exact figures or timestamps, provenance, or many records; use web results when they already answer the question. A search with sources: ["web"] omits semantic provider discovery; domainTools: true can still return website-matched tools. Web-only results use domainTools: false.

On an authenticated session, tool matches describe available capabilities; firecrawl_find_tools returns their contracts and firecrawl_scrape with an alexandria body executes a selected capability. Keyless sessions get no Alexandria matches in data.tools.

For a programming question, add categories: ["developer"]; its hits return in data.web with category: "developer". For a legal or regulatory question, categories: ["gov"] returns hits in data.web with category: "gov" and cannot be combined with other categories; authenticated sessions also have firecrawl_gov_search as the dedicated tool. categories: ["research"] restricts web results to research-affiliated websites; the firecrawl_research_* tools are a separate surface over paper abstracts and full text (PubMed, bioRxiv, medRxiv, arXiv). Query operators, domain filters, categories, toolDetail and scrapeOptions are described on their parameters. Returns source-type result groups and usage metadata. Authenticated responses can include an id for optional search feedback.

firecrawl_find_toolsA

Browse Alexandria data providers and workflows or read a selected contract. Alexandria covers companies, people, jobs, finance and filings, public records and government spending, real estate, places and restaurants, retail and prices, package registries and developer data, news, research, and more: typed, sourced records through published contracts. Prefer normal firecrawl_search for a data task; it already returns matching providers. Use this tool when the contract you need was not returned in full, to browse a category when search found nothing, or before scraping the same fields from several pages. Discovery is free. Use query for semantic discovery or urls to find providers for a website. With no arguments, browse categories, then providers and tools. Contracts describe the inputs and outputs for execution through firecrawl_scrape. nextTool identifies further discovery or pagination. Discovery does not execute providers. Use firecrawl_search when you also need web results.

firecrawl_crawlC

Start 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_statusA

Retrieve 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_agentA

Run web research that returns structured data when the URLs are not known or the answer spans several sites. Describe the fields you need in prompt, optionally pass a JSON schema and seed urls, and the research agent searches, navigates, reads pages, and returns JSON assembled across sources. Use it to research an entity plus its fields (founders, pricing, contact details), to build lists and datasets (companies, people, products, jobs, papers), and for pages that need navigation or interaction to reach the data. Optional effort sets the reasoning budget, maxCredits caps spend, and strictConstrainToURLs keeps the agent to the supplied urls.

This call returns only a job ID, not the research result. Read the job with firecrawl_agent_status until it reaches completed or failed; a typical research run takes one to three minutes. For one known URL use firecrawl_scrape (with formats: ["json"] for structured output); for a plain lookup that a results page answers, use firecrawl_search.

The job also returns a threadId. To continue that thread, pass it with a follow-up prompt; omitted mode, urls, schema and exchange settings carry over from the previous turn.

The agent only calls Alexandria providers whose terms the team has accepted. exchange.skippedProviders lists gated providers. With exchange.onTermsRequired "ask", a terms pendingApproval and exchange.requiresAction carry the approvalId and provider requirements. Read terms/show through firecrawl_scrape. An organization admin must accept terms in the Firecrawl dashboard at the provider URL or https://www.firecrawl.dev/app/settings?tab=data-sources. Ignore any terms/accept call in the API response. Only after the admin confirms acceptance, resume with the same threadId and exchange.approve: {approvalId}; this does not accept terms. To decline, use exchange.decline: {approvalId}. Never infer acceptance from a data request.

firecrawl_agent_statusA

Retrieve 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; a typical research run takes one to three minutes and complex jobs can take longer. 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_interactA

Open 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_stopA

Stop the live interact session associated with a scrapeId and release its resources. Returns a success confirmation.

firecrawl_parseA

Parse 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. Authenticated final responses can include a data.metadata.scrapeId for optional parse feedback.

firecrawl_monitor_createA

Create 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.

firecrawl_monitor_listA

List monitors for the authenticated account with optional pagination controls. Returns one page of monitor records and pagination metadata.

firecrawl_monitor_getA

Retrieve one monitor by ID, including its configuration and current state. This does not run or modify the monitor.

firecrawl_monitor_updateA

Patch an existing monitor by ID. The body can change its name, active/paused status, schedule, targets, goal, judging, webhook, notifications, or retention; these changes affect future scheduled checks.

Returns the updated monitor.

firecrawl_monitor_deleteA

Permanently delete a monitor by ID and stop its future schedule. This operation cannot be undone and returns deletion status.

firecrawl_monitor_runA

Queue an immediate check for a monitor outside its normal schedule. This starts network work for the monitor's configured targets and returns the queued check.

firecrawl_monitor_checksA

List historical checks for a monitor, optionally filtered by status and bounded by a result limit. Returns one page of check summaries and pagination metadata.

firecrawl_monitor_checkA

Retrieve one monitor check and its page-level results, optionally filtered by page status. Pages report same, new, changed, removed, or error; configured goal judging can add a meaningful-change decision.

Markdown tracking returns a unified text diff, JSON tracking returns field paths with previous/current values and a current snapshot, and mixed tracking returns both. Returns one page of results plus a next URL when more pages exist.

firecrawl_research_search_papersA

Search paper metadata and abstracts with a natural-language query across the indexed corpus, which spans biomedical, life-science, and clinical literature (PubMed, bioRxiv, medRxiv) alongside arXiv and other scientific sources. Optional author, category, and date filters constrain results.

Several distinct framings of the same question surface different papers than a single query does.

Returns ranked papers with canonical IDs, titles, authors, and abstracts.

firecrawl_research_inspect_paperA

Retrieve canonical metadata for one paper ID, such as an arXiv, PMC, PMID, or DOI identifier. Returns the title, abstract, authors, categories, source IDs, and dates as markdown.

firecrawl_research_related_papersB

Find citation-graph candidates from one to ten seed_ids; the first ID is the primary seed and later IDs are anchors. mode defaults to similar (co-citation/bibliographic coupling); citers returns papers citing a seed and references papers cited by a seed. intent ranks candidates.

Returns ranked candidates and the evaluated pool size.

firecrawl_research_read_paperA

Retrieve in-body passages from one paper that are relevant to a specific question. Full text is available only for indexed papers; k controls the number of passages.

Returns matching passages or a notice when full text is unavailable.

firecrawl_developer_searchA

Search an index of public repositories, GitHub issues, merged pull requests, repository READMEs, and code documentation for programming questions that need external documentation or upstream evidence.

Returns ranked results with an ID, source type, URL, title, and the matched passages in markdown.

firecrawl_gov_searchA

Search an index of primary law and regulatory material from US federal, state, and local government sources (statutes, regulations, codes, court opinions, and other government publications) for legal or regulatory questions that need the governing text or an official source.

Returns ranked results with a position, title, URL, and matched snippet.

firecrawl_credit_usageA

Get the authenticated Firecrawl team's current credit balance or historical credit consumption. Use the current view to answer how many credits remain or to check billing-period boundaries. Use the historical view for monthly usage reporting and trend analysis.

The current view returns remainingCredits, planCredits, billingPeriodStart, and billingPeriodEnd. Extra purchased or granted credits can make remainingCredits greater than planCredits. Billing-period dates may be null when the upstream billing provider has no period metadata.

The historical view returns periods sorted by start date with startDate, endDate, and creditsUsed. Set byApiKey to include separate periods per API key, identified by the optional apiKey field. The newest period's endDate can be null.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 26 tools

Disambiguation4/5

Most tools target a clearly distinct resource+action (scrape vs map vs crawl vs parse vs interact), and the specialized searches (developer, gov, research, web) are scoped by source domain. The weakest boundaries are firecrawl_monitor_check vs firecrawl_monitor_checks and firecrawl_search vs firecrawl_find_tools, both of which require reading the descriptions to separate.

Naming Consistency4/5

A predictable firecrawl_<noun>_<action> snake_case pattern dominates (scrape, map, crawl, monitor_create/update/delete, research_*_paper). A few names drop the verb or invert order — firecrawl_agent_status, firecrawl_credit_usage, firecrawl_find_tools — which are minor deviations but still readable.

Tool Count3/5

At 26 tools the surface is heavy, though the server genuinely spans several domains (scrape/crawl, agent, monitors, research, specialized search, billing). The monitor family alone is seven tools, and some pairs (monitor_run, agent_status) could plausibly be folded into existing operations.

Completeness4/5

Coverage is broad and lifecycle-complete in most areas: monitors have full CRUD plus run/checks, interact has a stop, agent has status polling, and research papers have search/inspect/related/read. Minor gaps remain — no crawl cancellation or batch-scrape operation, and job control is limited to read-only status checks.

Maintenance

ActivitySlowing
ResponsivenessNo recent community issues