Firecrawl MCP Server vs Gaff Check

A side-by-side look at the Firecrawl MCP Server and Gaff Check MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Firecrawl MCP Server logoFirecrawl MCP ServerSearch & Data Extraction · Local subprocess (stdio)Official Firecrawl server to search the web and scrape, crawl, map, and extract structured data from any site for LLMs. Handles JS-rendered pages, PDFs, and batch jobs; hosted remote MCP with OAuth or self-host.90ExcellentAuth: api key requiredGaff Check logoGaff CheckReal Estate · Local subprocess (stdio)Irish property due diligence for AI agents: planning, sold prices, radon, zoning, flood, BER.61GoodAuth: not declared

Verdict: choose Firecrawl MCP Server for search & data extraction work as a local process; choose Gaff Check for real estate as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Firecrawl MCP Server logoChoose 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.
Explore Firecrawl MCP Server

Gaff Check logoChoose Gaff Check when

  • You need dedicated capabilities in the Real Estate domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like resolve_location, planning_applications, sold_prices.
Explore Gaff Check

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFirecrawl MCP Server logoFirecrawl MCP ServerGaff Check logoGaff Check
CategorySearch & Data ExtractionReal Estate
Quality signal90/100 · Excellent61/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNot declared
PricingFreemiumNot declared
Required env varsFIRECRAWL_API_KEYHTTP_STREAMABLE_SERVERNone listed
Verified owner VerifiedCommunity listing
GitHub stars7,6738
Directory activity 14 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools258

Tools & capabilities

Firecrawl MCP Server tools 25

  • firecrawl_scrape Retrieve 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_map 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`.
  • firecrawl_search Search 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_crawl 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_status 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_extract Deprecated 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_agent Start 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_status 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`; 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_interact 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_stop Stop the live interact session associated with a `scrapeId` and release its resources. Returns a success confirmation.
  • firecrawl_parse 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.
  • firecrawl_monitor_create 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.
  • +13 more on the listing page

Gaff Check tools 8

  • resolve_locationResolve a free-text Irish address or place name to geographic coordinates (WGS84 lat/lng), returning ranked candidate matches. Use this first when the user gives an address, street, townland, or place name in Ireland, to confirm the correct location before calling other gaff-check tools — every candidate echoes its full resolved name so you (and the user) can sanity-check the match. If you already have exact lat/lng coordinates, you do not need this tool. Geocoding uses OpenStreetMap Nominatim and is best-effort: rural addresses and new estates may match poorly, and Eircodes only resolve where OSM mappers happen to have added them (there is no licensed Eircode lookup — if the user has only an Eircode, ask for the address or an approximate location instead). The confidence score ranks candidates within one query; it is not an absolute probability. Coordinates are WGS84 decimal degrees.
  • planning_applicationsFind Irish planning applications near a location, from the National Planning Application Database (all 31 local authorities, coverage back to ~2010, updated on varying cadences). Use this for property due diligence: pending or recent developments near a home (apartment blocks, roads, masts), extensions and attic conversions on the same street (precedents for what gets approved), and refusals that hint at site constraints. Returns per application: reference number, local authority, development description, address, status, decision with dates, distance in metres from the query point, and a link to the local authority's planning file where available. Provide either lat/lng (WGS84) or a free-text address (geocoded via OpenStreetMap; the resolved location is echoed back — verify it matches before drawing conclusions). Dates are ISO YYYY-MM-DD. The 'decided'/'pending' filter is based on whether a decision date is recorded; raw status strings vary by local authority and are returned verbatim. Coordinates of some older applications are approximate, and update lag differs by authority — absence of results is not evidence that nothing is planned.
  • sold_pricesLook up actual sold prices of residential properties in Ireland from the official Property Price Register (PSRA), which records declared prices from stamp-duty filings since January 2010. Use this to see what properties actually sold for near a property of interest: filter by county (required — the register is organised by county), a free-text address fragment (e.g. a street or estate name), an Eircode routing key (first 3 characters, e.g. 'D06' — only present on more recent records), a date range, and/or a price range. Returns per sale: date, declared price in EUR, address as recorded, Eircode where recorded, new vs second-hand, and flags for not-full-market-price and VAT-exclusive sales. Results are newest first. Know the data's limits: addresses are free text typed from stamp-duty returns — spelling varies, many records lack Eircodes, and address matching is substring-based, so try street name alone before street + number. There is no floor area, so price-per-square-metre cannot be derived. Prices on new builds are often VAT-exclusive (flagged), and declared-price errors exist in the register. This tool reports records, not valuations. If the user has no county, ask them (or infer it from the address) before calling.
  • radon_riskGet the EPA's radon risk classification for the area containing a location in Ireland. Radon is a naturally occurring radioactive gas and the second biggest cause of lung cancer in Ireland after smoking. Use this during property due diligence to learn the area's banding from the EPA Radon Risk Map: the result echoes the EPA's own wording ("About 1 in N homes in this area is likely to have high radon levels", where N is 5, 10 or 20 — lower N means higher risk) plus a high_radon_area flag (true for the 1-in-5 and 1-in-10 bands, the ≥10% threshold Ireland uses to designate High Radon Areas, which carry legal testing duties for workplaces). This is an area-level prediction from measurement and geological data — it is NOT a measurement of any specific home. The EPA's standing advice ships in every response: any home anywhere can have high radon regardless of banding, the only way to know is to test, and testing is cheap (~€50). Provide lat/lng (WGS84) or a free-text address (geocoded; resolved location echoed back).
  • zoningGet the generalised land-use zoning for a location in Ireland, from the Myplan.ie composite of all current local authority development plans. Use this in property due diligence to learn what the land is zoned for — residential, agricultural, open space, industrial, mixed use, etc. Zoning tells you what could be built there (or next door), whether a site has development potential, and whether a use is likely permissible. Returns the generalised zone type (standardised across authorities, e.g. 'Existing residential'), the local authority's own original zone label and objective text, the development plan name with its validity dates, and a link to plan documents where available. Provide lat/lng (WGS84) or a free-text address (geocoded; resolved location echoed back). Important: generalised zoning is a standardised simplification that complements but does NOT replace the statutory development plan — zone boundaries are generalised, and specific objectives, conditions and designations (protected structures, flood zones, SACs) live in the written plan. Verify anything decision-critical against the local authority's plan via the link. Points on unzoned land (much of rural Ireland outside town plans) return no records; that means no zoning objective is mapped, not that development is impossible.
  • flood_riskCheck mapped flood context for a location in Ireland: groundwater flood probability (high/medium/low), maximum historic groundwater flooding, and observed winter 2015/2016 surface-water flooding, from Geological Survey Ireland's 1:20,000 mapping. Use this in property due diligence. For each layer you get: whether the point itself lies inside a mapped extent (at_point), how many extents fall within the search radius, and the distance in metres to the nearest one. Groundwater flooding (turloughs, high water tables) is a distinct hazard from river or coastal flooding and matters especially in karst limestone areas of the west and midlands. CRITICAL LIMITATION — this tool does NOT check river (fluvial) or coastal flood models. The OPW's national flood extent datasets are licensed CC-BY-NC-ND, which forbids serving derived query results, so results include unchecked entries for them pointing to the OPW's official viewer (floodinfo.ie) where the user can view all flood maps for the location. A property can be at serious river or coastal flood risk while showing nothing in this tool's results. Never interpret empty results as "no flood risk": mapping is not exhaustive, pluvial (rain) flooding is not mapped at all, and the fluvial/coastal layers are not queried. Absence of a mapped extent means exactly that and no more. Provide lat/lng (WGS84) or a free-text address (geocoded; resolved location echoed back). Insurance decisions use different, private data — this tool says nothing about insurability.
  • ber_contextGet Building Energy Rating (BER) context for an area of Ireland: the distribution of BER grades (A1 best … G worst) among certified dwellings in a county or Dublin postal district, optionally narrowed to a construction era, plus current SEAI retrofit grant amounts. Use this to answer "what energy rating is typical for a house of this age around here?" and "what upgrade grants exist?" during property due diligence. Data is CSO statistics aggregated from BER certificates published since 2009 — e.g. 1978-1999 houses in Co. Galway cluster around C/D, while 2015+ builds are overwhelmingly A-rated. Areas accepted: the 26 counties, the cities (Dublin/Cork/Galway/Limerick/Waterford), or Dublin postal districts ('Dublin 9', 'D6W'). Construction periods: 1700-1977, 1978-1999, 2000-2004, 2005-2009, 2010-2014, 2015-2019, 2020-2024, 2025-2029. THIS TOOL CANNOT TELL YOU A SPECIFIC HOME'S BER — never present the area distribution as the property's rating. A home's actual BER is on its certificate: the seller/agent must provide it, or it can be looked up on SEAI's public register (link included in every response) with the BER number or MPRN. Note also the statistics' bias: only dwellings that needed a certificate (sold, rented, grant-aided, or new since 2009) are counted, so old housing stock that never transacted is under-represented and its true typical rating is likely worse than shown. Grant amounts are a static reference with a last-verified date — confirm on seai.ie before financial decisions.
  • recorded_crime_contextGet recorded-crime context for the Garda sub-district containing an Irish location, using official CSO counts and current Garda administrative boundaries. Use this for factual questions such as "what categories of crime have been recorded in this wider Garda area?" or to supply category-specific values for a choropleth. It returns annual counts, a pooled annual average, rates per 1,000 Census 2022 residents with approximate 95% Poisson intervals, and optionally the latest four-quarter Garda Division trend. Provide WGS84 lat/lng or a free-text address. Offence groups use official broad codes 03–16; omit them to return all published local groups. This is NOT a street-level crime heatmap or a property safety assessment. CSO station data applies to the entire Garda sub-district polygon: incidents have no published coordinates and may have happened anywhere within it. Never infer a hotspot near the address, spread incidents evenly across the polygon, combine categories into a score, or label the property/area safe or unsafe. Homicide (01) and sexual offences (02) are not published at this local resolution and are explicitly reported as unchecked. Resident-based rates are weak in city centres, airports, retail and nightlife areas with large non-resident populations; enforcement activity also affects some categories. Recorded incidents use PULSE report dates, can be revised, and are not a measure of all crime experienced. Fraud has a 2023 break and a narrower public-reported series from 2024.

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.

Firecrawl MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "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"
      }
    }
  }
}

Gaff Check

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "gaff-check": {
      "command": "npx",
      "args": [
        "-y",
        "gaff-check"
      ]
    }
  }
}

Frequently asked questions

Firecrawl MCP Server is categorized under Search & Data Extraction and uses a local stdio subprocess. Gaff Check belongs to Real Estate and uses a local stdio subprocess. Pick Firecrawl MCP Server for search & data extraction work and Gaff Check for real estate.

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.

Firecrawl MCP Server is listed as freemium — a free tier with paid plans. Auth: api key required. Gaff Check has no declared pricing — check the project's own site. 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 firecrawl-firecrawl-mcp-server and gaff-check as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Firecrawl MCP Server has a quality signal of 90/100 (Excellent) with 14 views, 0 installs and 7,673 GitHub stars. Gaff Check has 61/100 (Good) with 1 views, 0 installs and 8 GitHub stars.