How to connect Firecrawl to Cursor

Checked against Cursor's documentation on Oct 26, 2026. Commands and config blocks are generated from the same install data as each listing page.

1. 1. Check what you need

   Cursor reaches this server over the network, so there is no package or runtime to prepare on your side.

   • It can take Authorization (next step).

2. 2. Get Authorization

   The listing describes an optional Firecrawl API key, sent as a bearer value. Create one in your Firecrawl account if you plan to use it.

   • Authorization (optional): Optional. Bearer <FIRECRAWL_API_KEY>. Get a key at https://firecrawl.dev/app/api-keys.

3. 3. Add Firecrawl MCP Server to Cursor

   Cursor needs the hosted address and an Authorization header that expands a variable by name. Export that variable in the environment Cursor starts from, as the block shows.

   {
     "mcpServers": {
       "firecrawl-mcp-server": {
         "url": "https://mcp.firecrawl.dev/v2/mcp",
         "headers": {
           "Authorization": "${env:FIRECRAWL_MCP_SERVER_TOKEN}"
         }
       }
     }
   }

   Copy

   export FIRECRAWL_MCP_SERVER_TOKEN="Bearer paste-your-token-here"

   Copy

   • Cursor expands ${env:NAME} from its own environment, so the variable has to be set where Cursor starts.

4. 4. Restart or reload if it does not appear

   Use this step if Firecrawl MCP Server is not visible yet; it gathers Cursor's restart wording and the approval prompt.

   • The docs do not say whether editing mcp.json needs a restart. They tell you to restart Cursor after updating files of a custom local server.
   • Cursor asks for approval before an agent uses an MCP tool unless you allowlist it.