The Amazon Q Developer CLI is now the Kiro CLI. For terminal use, follow the Kiro setup.
Quick setup
- Open your IDE, then the Q Developer panel, then the Chat panel.
- Select the tools icon, then the plus (+) button.
- Choose a scope: global stores the server in
~/.aws/amazonq/default.json, and local stores it in.amazonq/default.jsonin the project. - Enter
firecrawlas the name, choose http as the transport, and enter this URL:
- Select Save. Q Developer opens a browser page for you to authorize access. Sign in to Firecrawl and approve the connection.
- Review each tool’s permission (Ask, Always allow, or Deny) in the panel that appears after saving.
Prefer to edit the configuration file?
Prefer to edit the configuration file?
Q Developer also reads MCP servers from Support for the
~/.aws/amazonq/mcp.json (global) and .amazonq/mcp.json (project):mcp.json files is controlled by the useLegacyMcpJson field in default.json, which is true by default.Prefer an API key?
Prefer an API key?
In the same dialog, add a header named
Authorization with the value Bearer fc-YOUR-API-KEY and use https://mcp.firecrawl.dev/v2/mcp as the URL. See Configure an API key.Try it
What you can do
Search
Find current information and read the content of relevant results.
Scrape
Turn URLs into clean markdown or structured data.
Interact
Navigate, click, and fill forms to reach the data you need.
Alexandria
Discover structured data tools, inspect inputs and pricing, then run them through Firecrawl.
Troubleshooting
- A “Fix Configuration” alert appears: select it to return to the form and check the URL.
- The browser page does not open: choose Edit setup for the server, save again, and complete the authorization when the page opens.
- The server is listed but its tools do not run: open the server in the MCP Servers panel and confirm it is enabled and the tools are not set to Deny.
- Two Firecrawl entries: a server in
.amazonq/default.jsontakes precedence over the global one. Remove the duplicate you do not want.

