We are launching Spidra's MCP server today, and this is not a "why Spidra beats everyone else" post. The scraping tools already inbuilt inside MCP clients right now are good, but just a few of them are excellent at things Spidra does. Below is an honest map of where the money goes, how the tools are actually built, and where Spidra sits between them.
Three different bets on what an MCP scraping tool should be
If you strip away the marketing pages, only three genuinely different architectures show up. 1. Playwright MCP bets on giving you nothing but a browser. Playwright MCP is free, open source, and runs entirely on your own machine. There is no credit system because there is no hosted service: you install it with npx, it drives a real Chromium, Firefox, or WebKit instance, and it hands your AI client structured accessibility snapshots of whatever page is open rather than screenshots. That is a meaningfully different approach from either of the two above. Instead of an AI model interpreting a scraped result, it reads the page's accessibility tree directly, the same information a screen reader would use, and lets the model click and type using element references from that tree. It is the right tool if your team already runs Playwright in production and wants an agent that can drive the same browser setup. It is also the tool where you own every proxy, every CAPTCHA, and every bit of infrastructure that keeps a headless browser from getting blocked, none of which Playwright MCP handles for you.
2. Apify bets on being a marketplace. The Apify MCP server does not scrape anything itself. It hands your AI client access to Apify Store, a catalog of more than 62,000 community-built programs called Actors that do everything from pulling Amazon listings to running Google Maps searches. You are not paying for a scraper; you are paying for compute time on whichever Actor gets called, priced from $0.13 to $0.20 per compute unit depending on your plan, on top of a monthly prepaid balance that ranges from free (with $5 of usage) up to $999 a month before you talk to sales.
3. Firecrawl bets on being a context API. Instead of a marketplace, Firecrawl gives you a fixed set of endpoints (scrape, crawl, map, search, interact) that all return clean markdown or structured JSON, billed by credit rather than compute time. A credit buys you one page for scrape, crawl, or map, two credits buys ten search results, and two credits buys a minute of interactive browser time. Pricing runs from a free tier (1,000 credits a month) through Hobby at $16, Standard at $83, Growth at $333, up to Scale at $599 a month for a million credits.
A simple three-column comparison graphic. Marketplace, Context API and Bring your own browser
Where Spidra sits
Spidra is closer to Firecrawl's shape than Apify's. There are no third-party Actors, and no compute unit billing. You get twelve tools through one hosted endpoint, https://mcp.spidra.io/mcp
, documented in full here, and every one of them is designed to be used through plain English rather than a schema you memorize first.
That last part is the actual bet Spidra is making, and it is worth explaining rather than asserting. Before this launch, the team ran the twelve tools through a structured test plan covering every tool at least once: a single page scrape, a merged comparison across two or three sites, structured field extraction, a 5 URL batch job with independent results per URL, a site crawl capped at a page limit, cancelling a batch or crawl mid run without losing what had already finished, re-extracting new fields from an already completed crawl without re-fetching a single page, and checking job history and credit usage after the fact. None of those test cases involved writing a line of code.
The tool list itself reflects that split between one-shot and long-running work:
| Tool | What it does |
|---|---|
spidra_scrape |
Scrape 1 to 3 URLs and return the result |
spidra_check_scrape_status |
Check a scrape that ran past its initial wait window |
spidra_batch_scrape |
Process 2 to 50 URLs in parallel, each kept separate |
spidra_check_batch_status |
Check batch progress and pull completed results |
spidra_cancel_batch |
Cancel a running batch, keep what already finished |
spidra_crawl |
Crawl a site from one target URL |
spidra_check_crawl_status |
Check crawl progress and completed pages |
spidra_crawl_pages |
Pull individual crawl pages and download links |
spidra_crawl_extract |
Run a new extraction over a crawl that already finished |
spidra_cancel_crawl |
Cancel a running crawl, keep what already finished |
spidra_scrape_logs |
Look up past jobs and their outcomes |
spidra_usage |
Check request, credit, and token usage |
The distinction that matters here, and the one that trips up a surprising number of MCP scraping setups, is between a batch and a crawl. A batch takes a list of URLs you already know and returns one independent result per URL, so five product pages come back as five rows, not one blended answer. A crawl starts from a single URL and follows links Spidra discovers on its own, which is the right tool when you want "get me every blog post on this domain" rather than "** get me these five specific pages**."
What the numbers actually look like side-by-side
Pricing across these tools is not measured in the same units. Here is the closest version, using each tool's own published numbers as of August 2026.
| Tool | Free tier | Entry paid plan | Billing unit |
|---|---|---|---|
| Spidra | 300 credits, one time, no card | $19/month for 5,000 credits | Credits per action |
| Firecrawl | 1,000 credits/month, keyless | $16/month for 5,000 pages (billed yearly) | Credits per page or per browser minute |
| Apify | $5/month of platform usage | $29/month + pay as you go | Compute units, from $0.20/CU |
| Playwright MCP | Everything, forever | No paid tier exists | Nothing, you run your own browser |
A word on what "credits" mean in practice: Spidra's pricing page lists Starter at 5,000 credits a month for $19, Builder at 25,000 credits for $79, and Pro at 125,000 credits for $249, alongside proxy bandwidth allowances and a rising cap on concurrent requests and actions per URL as you move up. Firecrawl's credit costs are published per feature (1 credit per page for scrape, crawl, or map, 2 credits per 10 search results, 2 credits per browser minute for interact), which makes it easier to estimate a monthly bill in advance if your workload is mostly one feature. Apify's compute unit pricing is the hardest to estimate ahead of time, because the cost of an Actor run depends on the Actor's own memory footprint and runtime, not a flat per-page rate, though Apify's dashboard shows the actual cost after each run so you are not billed blind for long.
Trying it today
The Spidra MCP server is live at https://mcp.spidra.io/mcp
as of today, August 24th, 2026. The same URL works for Cursor, VS Code, Windsurf, Claude Code, Codex, and a handful of other clients, each documented with exact configuration snippets at docs.spidra.io/mcp-server.
If you try it and a tool does something the docs did not lead you to expect, that gap is worth reporting rather than working around.
Sign up for a free account at [app.spidra.io](https://app.spidra.io/signup) to try it out.