← All recipes

MCP Recipe

Scrape docs, then check the current API with Firecrawl and Context7

Influzer starter recipe: use Firecrawl to pull a documentation page, then Context7 to fetch versioned library docs so the agent answers against current APIs instead of training-data guesses.

Engineering
By Influzer Published 2026-10-11 Updated 2026-10-11 0 worked for me

MCP servers used

Compatible clients (author-reported, not verified by Influzer): Cursor, Claude Desktop, ChatGPT

Prerequisites

  • Firecrawl remote MCP access (account / API key as required by Firecrawl)- Context7 remote MCP access- A public docs URL you are allowed to scrape

Required permissions

Firecrawl needs permission to fetch the target URL. Context7 needs access to its docs index. Do not paste API keys into recipe fields — configure them in your client secrets or OAuth flow.

Setup

1. Connect both remote servers

Add Firecrawl (https://mcp.firecrawl.dev/v2/mcp) and Context7 (https://mcp.context7.com/mcp) in your client. Complete any OAuth or API-key setup those hosts require.

2. Example dual-server mcp.json · json
{  "mcpServers": {    "firecrawl": {      "url": "https://mcp.firecrawl.dev/v2/mcp"    },    "context7": {      "url": "https://mcp.context7.com/mcp"    }  }}
3. Scrape, then verify against current docs · markdown
1) Use Firecrawl to scrape https://docs.stripe.com/payments/accept-a-payment and extract the first-steps overview.2) Use Context7 to fetch current Stripe Node docs for creating a PaymentIntent.3) Summarize what changed or what I should implement first. Prefer Context7 for API shapes; use the scraped page for product flow.
4. Keep secrets out of the prompt

If the agent asks for keys, configure them in the MCP server settings. Use placeholders like YOUR_STRIPE_SECRET_KEY in any example code it writes.

Expected result

A short answer that cites both the scraped page and Context7’s current docs, with library/version context when available.

Sample output

From the scraped getting-started page, auth uses an Authorization header with an API secret.Context7 for stripe (current docs) shows the PaymentIntent create shape…

Troubleshooting

  • Firecrawl auth errors: reconnect the Firecrawl MCP / rotate the key in the client, not in chat- Context7 misses a library: try the canonical package name (e.g. next, stripe)- Never paste live secrets into prompts

Report an issue