feat: add configurable timeout for crawl operations #136
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
FIRECRAWL_CRAWL_TIMEOUTandFIRECRAWL_CRAWL_POLL_INTERVALenvironment variables to control crawl job behaviorProblem
The
firecrawl_crawltool callsclient.crawl()which polls indefinitely until the crawl job completes. For large sites or slow self-hosted instances, this can cause the MCP server to appear frozen/hung, making the tool unusable.Solution
FIRECRAWL_CRAWL_TIMEOUTto adjust (in seconds)FIRECRAWL_CRAWL_TIMEOUT=0to restore the original indefinite wait behaviorFIRECRAWL_CRAWL_POLL_INTERVAL(default: 2 seconds)Changes
src/index.ts: Parse timeout/poll interval from environment variables, pass toclient.crawl()README.md: Document new configuration optionsFixes #103