Specific implementation researched
Firecrawl
Implementation, permissions and documented client compatibility.
A directory listing or verification does not replace a security audit. No installation is triggered automatically here. Do not enter API keys in public forms.
What is specifically documented?
- Connected service
- Firecrawl
- Publisher
- Firecrawl
- Origin
- Officially from the named publisher
- Deployment mode
- Remote
- Transport
- HTTP
- Authentication
- OAuth at the mcp-oauth endpoint; API key as a bearer token at the separate /v2/mcp endpoint; limited keyless access.
- Read capabilities
- Web search · Scrape web pages · Parse content
- Write capabilities
- No confirmed information
- Permissions
- Authenticated functionality depends on the team and plan; anonymous features are subject to daily limits.
- Required plan
- No confirmed information
- Additional costs
- No confirmed information
- Maintenance status
- No confirmed information
- Review date
- 11/10/2026
Support by client
Documented setup is not an independent functional test. General MCP support does not imply full compatibility.
| Client | Status | Source |
|---|---|---|
| Claude Desktop | Setup documented | Documentation ↗ |
| Claude Code | Setup documented | Documentation ↗ |
| Claude Web | Setup documented | Documentation ↗ |
| Cursor | Setup documented | Documentation ↗ |
Sources & implementation
Firecrawl MCP: Get Started ↗Retrieved on 11/10/2026. Provider statements, not a security audit.
Implementation: https://mcp.firecrawl.dev/v2/mcp-oauth