Kiro CLI replaces the Amazon Q Developer CLI. If you used
q before, this page applies to you.Quick setup
- Open the user-level configuration file
~/.kiro/settings/mcp.json. In the IDE, run Kiro: Open user MCP config (JSON) from the command palette. For a single project, use.kiro/settings/mcp.jsonin the workspace instead. - Add Firecrawl and save the file:
- Kiro reconnects when you save and opens the Firecrawl authorization page in your browser. Sign in and approve access.
- Open the MCP servers tab in the Kiro panel, or run
kiro-cli mcp status --name firecrawl, and confirm that Firecrawl’s tools are available.
Prefer an API key?
Prefer an API key?
Remote servers in Kiro accept headers. Export Kiro only expands environment variables you have approved. When it shows the security warning for
FIRECRAWL_API_KEY in your shell, then use:FIRECRAWL_API_KEY, approve it, or add it under Mcp Approved Env Vars in settings.Prefer the CLI?
Prefer the CLI?
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
- MCP support is off: in the IDE, open settings with
Cmd/Ctrl + ,, search for “MCP”, and enable it. - The server does not connect: confirm the URL is exactly
https://mcp.firecrawl.dev/v2/mcp-oauthand save the file again to trigger a reconnect. - An OAuth scope error appears: add
"oauth": { "oauthScopes": [] }to the server entry. - Workspace and user files both define
firecrawl: Kiro merges them and the workspace file wins. Keep one entry.

