Firecrawl MCP Tools Failures: `extract` Instability and Unimplemented `deep_research`/`generate_llmstxt`

During systematic testing of Firecrawl tools exposed via an MCP (Multi-Capability Platform) server integration, several tools consistently failed across multiple attempts. This issue details the problems encountered with mcp_local_firecrawl_firecrawl_extract, mcp_local_firecrawl_firecrawl_deep_research, and mcp_local_firecrawl_firecrawl_generate_llmstxt.

Affected Tools:

1. mcp_local_firecrawl_firecrawl_extract
2. mcp_local_firecrawl_firecrawl_deep_research
3. mcp_local_firecrawl_firecrawl_generate_llmstxt

Observed Behavior & Errors:

1. mcp_local_firecrawl_firecrawl_extract:

   • Initial tests and retries failed.
   • Error messages received included:
     • Error: no result from tool. The user likely interrupted the tool call to send you a message.
     • Request failed with status code 500 (Internal Server Error) when attempting to extract from https://docs.firecrawl.dev/introduction)
   • Analysis: While the core Firecrawl documentation confirms the extract feature (https://docs.firecrawl.dev/introduction), its implementation or configuration within the tested MCP server environment appears unstable or faulty, leading to inconsistent errors and failures.

2. mcp_local_firecrawl_firecrawl_deep_research:

   • Initial tests and retries failed.
   • Error messages received included:
     • Error: no result from tool. The user likely interrupted the tool call to send you a message.
     • Error calling tool: Tool mcp not found.
   • Analysis: Documentation review for firecrawl-mcp-server (across various commits/branches) did not show evidence of a deep_research tool implementation. It's suspected that this tool, despite being listed as available by the MCP environment, is not actually implemented in the version of firecrawl-mcp-server being run, causing the "Tool not found" errors.

3. mcp_local_firecrawl_firecrawl_generate_llmstxt:

   • Initial tests and retries failed.
   • Error messages received consistently included:
     • Error calling tool: Tool mcp not found.
   • Analysis: Similar to deep_research, documentation review for firecrawl-mcp-server did not show evidence of a generate_llmstxt tool. It's suspected that this tool, despite being listed as available by the MCP environment, is not actually implemented in the version of firecrawl-mcp-server being run.

Test Calls Attempted (Examples):

# Extract Attempt (Failed with 500 Error)
# print(default_api.mcp_local_firecrawl_firecrawl_extract(prompt="Extract the main features...", urls=["https://docs.firecrawl.dev/introduction"]))

# Deep Research Attempt (Failed with Tool Not Found / User Interrupted)
# print(default_api.mcp_local_firecrawl_firecrawl_deep_research(query="future of renewable energy", maxUrls=5, timeLimit=60))

# Generate LLMs.txt Attempt (Failed with Tool Not Found)
# print(default_api.mcp_local_firecrawl_firecrawl_generate_llmstxt(url="https://google.com"))

Environment Details (Client):

• Editor: Cursor
• Version: 0.48.9
• Commit: 1.96.2 (61e99179e4080fecf9d8b92c6e2e3e00fbfb53f0)
• Date: 2025-04-12T18:33:49.349Z
• Electron: 34.3.4
• ElectronBuildId: undefined (Note: Your provided info lists ElectronBuildId as undefined)
• Chromium: 132.0.6834.210
• Node.js: 20.18.3
• V8: 13.2.152.41-electron.0
• OS: Darwin x64 24.4.0 (Inferred from user info, OS version in your provided string seems different)

Expected Behavior:

• mcp_local_firecrawl_firecrawl_extract should execute successfully and return the extracted data or a clear error if the extraction itself fails (not a server/tool error).
• mcp_local_firecrawl_firecrawl_deep_research and mcp_local_firecrawl_firecrawl_generate_llmstxt should either:
  • Execute successfully if they are intended to be implemented.
  • Or, not be listed as available tools by the MCP server if they are not implemented, to avoid confusion.

Suggestion:

Could the maintainers please:

1. Investigate the stability and configuration of the extract tool within the MCP server context?
2. Verify whether deep_research and generate_llmstxt are intended features for firecrawl-mcp-server?
   • If yes, ensure they are correctly implemented and callable.
   • If no, update the MCP server's tool discovery mechanism to avoid listing unimplemented tools.

Thank you!