Best Fastly MCP MCP Server Alternatives 2026

Web content fetching and conversion for efficient LLM usage. Extract readable content from any URL.

Free and open-source by Anthropic. Fetches web content directly — no API key or paid service required.

The Apify MCP server gives AI agents access to 6,000+ ready-made cloud scrapers, crawlers, and automation tools on the Apify Store — no infrastructure required. Connect to Apify Actors that extract data from social media platforms (Instagram, TikTok, LinkedIn), search engines (Google, Bing), e-commerce sites (Amazon, eBay), maps (Google Maps), and virtually any website. Each Actor runs in the cloud with managed proxies, browser fingerprinting, and anti-bot bypass built in. Use the Apify MCP server to query Actors by task, stream results directly into your AI context, run custom scraping Actors from your Apify account, and chain multiple data extraction steps in a single workflow. Supports tool filtering to expose only the Actors you need, and integrates with Apify's RAG web browser Actor for retrieval-augmented generation use cases.

The MCP server is free and open-source. Apify platform: Free tier with $5/mo platform credits. Starter: $49/mo. Scale: $499/mo. Enterprise: Custom pricing.

AWS Labs maintains a monorepo of specialized, open-source MCP servers that bring AWS best practices directly into AI-assisted development workflows, spanning infrastructure, data, AI/ML, cost management, and healthcare/life-sciences domains. Rather than one monolithic server, the project ships dozens of focused servers you install individually depending on the task: the AWS Documentation MCP Server for real-time official docs and API references, dedicated servers for Terraform/CDK/CloudFormation infrastructure-as-code, container and serverless platforms (ECS, EKS, Lambda), SQL/NoSQL databases (DynamoDB, RDS, Aurora), search and analytics (OpenSearch), messaging (SQS/SNS), and cost/billing analysis. Most servers install via uvx with a package name like awslabs.aws-documentation-mcp-server, run locally over stdio, and use standard AWS credential chains (IAM roles, profiles, or access keys) rather than exposing raw account credentials to the model. AWS also now offers a managed, remote "AWS MCP Server" (in preview) that combines full API coverage with pre-built agent SOPs, syntactically validated API calls, and complete CloudTrail audit logging for teams that want centralized governance instead of running servers locally. The Getting Started with Kiro/Cursor/VS Code/Claude Code sections in the repo provide one-click install configs for each server, making it straightforward to wire up only the AWS services a given project actually touches.

The MCP server is free and open-source. AWS services use pay-as-you-go pricing. Free tier available for many services for 12 months. Costs vary by service usage.

Cloudflare ships two different things under this name. The mcp-server-cloudflare repo provides 16 remote, domain-specific MCP servers rather than one monolith — Documentation, Workers Bindings (storage/AI/compute primitives), Workers Builds, Observability (logs/analytics), Container sandboxes, Browser Rendering (fetch pages, convert to markdown, screenshots), Logpush health, AI Gateway (prompt/response search), AI Search, Audit Logs, DNS Analytics, Digital Experience Monitoring, Cloudflare One CASB, Radar, GraphQL analytics and the Agents SDK docs server, each on its own `*.mcp.cloudflare.com/mcp` hostname. Separately, the Cloudflare API MCP server at mcp.cloudflare.com/mcp (repo: cloudflare/mcp) exposes the whole 2,500+ endpoint Cloudflare API through just two tools, `search` and `execute`, using the Code Mode pattern — model-written JavaScript runs in an isolated Dynamic Worker, costing ~1,000 tokens of context against the ~1.17M an equivalent native-tool server would need. Pick a domain server when you want a readable, curated tool list for one product area; pick the API server for breadth or for endpoints nobody wrote a tool for. All endpoints are Streamable HTTP on `/mcp` and support the MCP 2026-07-28 spec; the historical `/sse` URLs remain as aliases for the same Streamable HTTP handler but no longer serve the deprecated HTTP+SSE transport, so clients pinned to SSE must switch. Auth is OAuth on connect, or a scoped Cloudflare API token as a bearer header for CI. Clients without native remote-MCP support bridge via `npx mcp-remote https://<subdomain>.mcp.cloudflare.com/mcp`.

The MCP server is free and open-source. Cloudflare: Generous free tier for Workers, KV, R2, D1. Workers Paid: $5/mo. Pro: $20/mo. Business: $200/mo.

Browserbase MCP and Stagehand MCP are the same server under two names, and this catalog lists both because people search for both — this page is the platform view, /servers/stagehand covers the natural-language automation layer that runs inside it. What Browserbase supplies is the browser itself: a headless Chrome session running in Browserbase's cloud rather than on the machine your agent is on, which is the reason to use it at all. The session is a real, addressable browser with its own residential-proxy and stealth configuration and a recorded replay you can watch afterwards, so an agent's browsing survives being run from a datacenter IP, and a failed run is debuggable after the fact instead of being a black box. Nothing renders on the developer's machine, so a long-running agent is not tied to a desktop staying awake. Browserbase's recommendation is the hosted server at https://mcp.browserbase.com/mcp over streamable HTTP — they operate it and absorb the model inference that the instruction-following tools require. Clients without HTTP transport connect via npx mcp-remote https://mcp.browserbase.com/mcp. Self-hosting installs @browserbasehq/mcp-server-browserbase from npm and needs BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID from your dashboard. Six tools are exposed — start and end for session lifecycle, navigate, act, observe and extract — and they are documented in detail on the Stagehand entry, because the act/observe/extract trio is Stagehand's model rather than Browserbase's. One thing to know before self-hosting: the browserbase/mcp-server-browserbase repository was archived on 2026-07-20 and its README now says it is kept for historical reference and should not be read as representative of the current production service. The npm package still installs and the star count on this page belongs to that archived repo; the hosted endpoint is the path Browserbase actually maintains.

The MCP server is free and open-source. Browserbase: Free tier with limited browser sessions. Paid plans for higher volume. See official pricing for current rates.

The Firecrawl MCP server gives your AI assistant the ability to crawl, scrape, and extract structured data from any website — turning raw HTML into clean, LLM-ready Markdown or JSON in seconds. Built by the Firecrawl team, it exposes tools for single-page scraping, deep site crawls (following internal links), and batch URL extraction, all with JavaScript rendering handled automatically so dynamic content is never missed. Developers use it to automate competitive research, build live knowledge bases, extract pricing tables, monitor documentation changes, or feed structured web data into RAG pipelines — all through natural-language prompts without writing a single scraper script. The Firecrawl MCP server handles rate limiting, retries, and proxy rotation behind the scenes. Authentication requires a Firecrawl API key (free tier available). Install with: npx firecrawl-mcp. Works with Claude Desktop, Cursor, VS Code, and any MCP-compatible client. With Firecrawl, any public webpage becomes a structured data source your AI can reason over, compare, and act on — making it the go-to MCP server for web data extraction workflows.

The MCP server is free and open-source. Firecrawl: Free tier with 500 credits. Hobby: $16/mo (3,000 credits). Standard: $83/mo. Growth: $333/mo.

The Notion MCP Server is the official integration from Notion that connects AI assistants directly to your Notion workspace via the Notion REST API. With 4,580+ GitHub stars, it is the canonical MCP tool for bringing Notion's knowledge management capabilities into Claude Desktop, Cursor, Windsurf, and any MCP-compatible client. The server exposes a rich set of tools: search your entire workspace by keyword and return matching pages and databases; retrieve full page content and block trees; create new pages inside any parent page or workspace section; update, append, or delete block content on existing pages; list all databases your integration has access to; query database entries with filter and sort parameters; retrieve individual blocks or nested children by block ID; and add comments to pages. Authentication uses a Notion integration token — create an internal integration at notion.so/my-integrations, share specific pages or databases with it, and set NOTION_TOKEN in your environment (the older OPENAPI_MCP_HEADERS form still works). Install with a single npx command. The Notion MCP Server is especially powerful for AI workflows that span documentation retrieval, project planning, and knowledge capture — Claude can read product specs from Notion, draft new pages from conversation output, log structured data into databases, and search across thousands of notes without any manual copy-paste.

The MCP server is free and open-source. Notion: Free for personal use. Plus: $10/user/mo. Business: $18/user/mo. Enterprise: Custom pricing.

The HubSpot MCP Server is HubSpot's hosted, official Model Context Protocol endpoint for Smart CRM data, reachable at https://mcp.hubspot.com and authorised with OAuth 2.0 — there is no package to install and no token to paste into a config file. Access is scoped by a HubSpot user-level app: you create one with read (and optionally write) scopes for the CRM objects you want an assistant to reach, then complete the OAuth flow from inside your client. Read and write coverage spans contacts, companies, deals, tickets, carts, products, orders, line items, invoices, quotes, subscriptions and lists, plus engagements — calls, emails, meetings, notes and tasks — and the associations between them. Organisational context (users, teams, reporting structures, owners, roles, seats) and marketing content (campaigns and their metrics, landing pages, website pages, blog posts) are read-only. Custom Sensitive Data Properties and Personal Health Information are excluded regardless of scopes. Two other things share the name and are commonly confused with this one: the Developer MCP server, installed locally with `hs mcp setup` from the HubSpot CLI and aimed at building HubSpot apps rather than querying CRM records, which requires Developer Platform v2025.2; and the original May 2025 public beta, an npm package configured with a private-app access token, which is what most third-party setup guides still describe. The server remains in beta and HubSpot advises experimenting in a developer sandbox and reviewing every write confirmation, since an LLM will occasionally propose a change to a system of record that it should not.

The MCP server is free and open-source. HubSpot CRM: Free tier available. Starter: $20/mo. Professional: $890/mo. Enterprise: $3,600/mo.

The Stripe MCP server is Stripe's official Model Context Protocol integration, and the first thing to know is that it is not a package you install — it is a remote server Stripe hosts at https://mcp.stripe.com, and the documented connection mechanism is OAuth, not an API key. For Claude Code that is `claude mcp add --transport http stripe https://mcp.stripe.com/` followed by `claude /mcp` to complete consent; Cursor and VS Code take the bare URL, and ChatGPT accepts it as a custom connector on Pro, Plus, Business, Enterprise and Education accounts. An administrator has to enable MCP access in the Dashboard first, separately for sandbox and for live mode, which is the usual cause of a connection that refuses to authorise. Rather than one tool per endpoint, four generic tools carry most of the surface — stripe_api_search, stripe_api_details, stripe_api_read and stripe_api_write — so the tool schemas do not consume the context window, alongside dedicated create_refund, get_stripe_account_info, stripe_report, stripe_implementation_planner and search_stripe_documentation tools, plus a Treasury balance summary in public preview. Supported API methods span customers, charges, refunds, PaymentIntents, Checkout Sessions, invoices, subscriptions, coupons, promotion codes, products, prices, payment links, disputes, webhook endpoints, balance and balance transactions, payouts, tax settings and registrations, and Issuing. Clients that cannot do OAuth pass a restricted API key as a bearer token; Connect platforms acting as a connected account must use a restricted key plus a Stripe-Account header, since OAuth cannot express that. Sessions are revocable from Dashboard user settings under OAuth sessions, and Stripe recommends human confirmation of tools given prompt-injection risk.

The MCP server is free and open-source. Stripe: Pay-per-transaction pricing at 2.9% + 30¢ per card charge. No monthly fees. Volume discounts available.

Turns your GraphQL API into MCP tools, from Apollo GraphQL itself. Rather than exposing a raw schema and hoping the model composes valid queries, the Apollo MCP Server takes a set of GraphQL operations you explicitly define and publishes each one as a named MCP tool, so an AI client calls a curated, tested operation instead of assembling ad-hoc GraphQL. It sits in front of a graph and needs three things configured: the graph itself, the operation definitions that become tools, and a config file describing how the server runs — all documented on the Apollo docs site. There are three ways to run it, which is the practical thing searchers want: the standalone binary (install with `curl -sSL https://mcp.apollo.dev/download/nix/latest | sh` on macOS/Linux, or the PowerShell `iwr` one-liner on Windows, and pin a version by swapping `latest` for e.g. `v1.17.0`); the Rover CLI via `rover dev --mcp <config>` (Rover v0.37+) to run the server alongside a local graph during development; and the Apollo Runtime Container, which can run the MCP server and the Apollo Router together in one container. Because tools map to predefined operations, you get persisted-query-style safety — the model cannot invent expensive or unauthorized queries — plus custom scalar handling, auth passthrough, CORS and error-handling controls covered in the config reference. Built in Rust, MIT licensed, actively maintained (released continuously), and the canonical repo is `apollographql/apollo-mcp-server`. This is the right MCP server for anyone exposing a GraphQL or federated supergraph to Claude, Cursor, or any MCP client. Compatible with all MCP-compliant clients over stdio and HTTP transports.

This MCP server is free and open-source. Check the GitHub repository for details.