From 78221eb45861ddd94544fe0cb10197d54fcfd449 Mon Sep 17 00:00:00 2001 From: "firecrawl-spring[bot]" <254786068+firecrawl-spring[bot]@users.noreply.github.com> Date: Sun, 3 May 2026 15:02:08 +0000 Subject: [PATCH] docs(use-cases): tighten developers-mcp value props Rewrite the two blurbs in "Why Developers Choose Firecrawl MCP" to lead with concrete reader benefits and remove redundancy with the page intro. Co-Authored-By: micahstairs --- use-cases/developers-mcp.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/use-cases/developers-mcp.mdx b/use-cases/developers-mcp.mdx index e4cfc68d..45a6d4ab 100644 --- a/use-cases/developers-mcp.mdx +++ b/use-cases/developers-mcp.mdx @@ -38,11 +38,11 @@ Your assistant picks the right tool automatically. Ask it to "read the Next.js d ## Why Developers Choose Firecrawl MCP -### Build Smarter AI Assistants -Give your AI real-time access to documentation, APIs, and web resources. Reduce outdated information and hallucinations by providing your assistant with the latest data. +### Ground answers in live data +Point your assistant at the documentation, APIs, and pages it actually needs. You get fewer hallucinations, fewer stale answers, and no manual copy-paste from a browser tab. -### Zero Infrastructure Required -No servers to manage, no crawlers to maintain. Just configure once and your AI assistant can access websites instantly through the Model Context Protocol. +### Skip the scraping infrastructure +You do not run servers, rotate proxies, or maintain crawlers. Configure your MCP client once and your assistant has the full Firecrawl toolset behind it. ## Customer Stories