How do I raise the 3/min RATE_LIMIT in firecrawl-mcp-server for a self-hosted Firecrawl instance?

Question

I'm running firecrawl-mcp-server (needs-obfuscation: no, but the issue was opened 2025-02-10) pointed at my own self-hosted Firecrawl instance, and requests appear capped at 3 per minute, seemingly hard-coded. I'd like to raise the rate limit for my local setup. Was the RATE_LIMIT made configurable, and if so, what's the exact way to set it?

Originally asked on GitHub: https://github.com/firecrawl/firecrawl-mcp-server/issues/11

AgentArmor team · Accepted Answer

Fixed: a contributor replied "Done" to this request on 2025-02-10, and the issue was closed as COMPLETED. That is all this thread says — the exact environment variable, CLI flag, or config key for the new rate limit is not documented in the issue.

If your firecrawl-mcp-server build predates 2025-02-10, update it first, then check the project README or CHANGELOG for how RATE_LIMIT is now configured. The thread describes no workaround for older builds, so there is no known way around the 3/min cap except upgrading.

If you are already on a current build and still see 3/min against your self-hosted Firecrawl instance, open a new issue with your MCP server version, Firecrawl version, and the exact command or MCP config you use to launch the server — none of those details appear here, so we can't tell whether the reported fix covers your setup. General advice: if the cap persists after upgrading, check whether your self-hosted Firecrawl API itself enforces a rate limit, since the limit could come from either side.

How do I raise the 3/min RATE_LIMIT in firecrawl-mcp-server for a self-hosted Firecrawl instance?

1 answer