Error: Missing fireCrawlApiKey when installing @mendableai/mcp-server-firecrawl via Smithery and Windsurf Pro

[Ranteck]

Summary When attempting to install @mendableai/mcp-server-firecrawl using the command provided by Smithery (with Windsurf Pro as the client), the process fails with an error stating that the required property fireCrawlApiKey is missing.

Setup

• Using Smithery to generate and paste the API key.
• Command provided by Smithery (run via CMD):

  npx -y @smithery/cli@latest install @mendableai/mcp-server-firecrawl --client windsurf --profile intellectual-clownfish-hFiJVB --key a6e1e1d4-80a5-487a-b23b-4c5e8a5d594e
  

• Client: Windsurf Pro
• Operating System: Windows 11

Error Output

Error: failed to initialize server: 2025-06-17T11:53:45.544Z [Runner] Connecting to server: {"id":"@mendableai/mcp-server-firecrawl","connectionTypes":["stdio"]}
2025-06-17T11:53:45.545Z [Runner] Starting child process setup...
2025-06-17T11:53:46.175Z [Runner] Error: Failed to fetch server connection: Registry request failed with status 400: {"error":"[{\"keyword\":\"required\",\"dataPath\":\"\",\"schemaPath\":\"#/required\",\"params\":{\"missingProperty\":\"fireCrawlApiKey\"},\"message\":\"should have required property 'fireCrawlApiKey'\"}]"}
2025-06-17T11:53:46.175Z [Runner] Final cleanup on exit: server terminated.

Steps to Reproduce

1. In Smithery, paste the provided API key.
2. Use the command above to attempt installation via CMD.
3. Observe the error output regarding the missing fireCrawlApiKey.

Expected Behavior The installation should proceed without an error if the API key is correctly supplied via Smithery.

Actual Behavior The installation fails with a missing fireCrawlApiKey error, despite providing the key through Smithery.

Additional Context

• Unsure if the API key needs to be set elsewhere or if there is a mismatch between what Smithery provides and what the MCP server expects.
• No prior successful installs with this workflow.
• Using Windsurf Pro in Windows 11.

Please advise on where or how the fireCrawlApiKey should be configured to resolve this error.

[patsevanton]

Same issue

work config:

{
  "mcpServers": {
    "firecrawl-mcp": {
      "command": "npx",
      "args": ["-y", "firecrawl-mcp"],
      "env": {
        "FIRECRAWL_API_KEY": "fc-xxxxxxxxx"
      }
    }
  }
}