This MCP server exposes a Firecrawl-powered set of endpoints through an Express-based local server used by the Firecrawl Power App UI. It integrates core Firecrawl MCP capabilities such as scraping, mapping, crawling, searching, extracting structured data, and running autonomous agents. Once the MCP server is running, the UI can communicate with it to perform tasks like scraping a webpage, discovering all URLs on a site, performing deep crawls with depth control, and extracting data using AI-driven schemas. Use the available API forms in the UI (Scrape, Map, Crawl, Search, Extract, Agent) to configure requests; the MCP backend translates these requests into Firecrawl API calls and returns structured results for display in the app.

Prerequisites:

• Node.js 18+ installed on your system
• Internet access to install dependencies

Step-by-step installation:

1. Clone the repository: git clone https://github.com/fracabu/firecrawl-power-app.git cd firecrawl-power-app

2. Install dependencies: npm install

3. Create an environment file (optional but recommended) and add your Firecrawl API key: cp .env.example .env

   Add your key to the .env file or set FIRECRAWL_API_KEY in your environment

   echo 'FIRECRAWL_API_KEY=your-api-key' >> .env

4. Start the MCP server (local development): npm run dev

5. Access the UI: Open http://localhost:5173 in your browser and enter your Firecrawl API key when prompted.

Notes:

• The MCP server entrypoint used here is server/api.js as part of the local Express server setup for development.
• If deploying elsewhere, configure your deployment platform to expose the same port and environment variable as needed.

Tips and caveats:

• The MCP server relies on a Firecrawl API key. Keep this key secure and do not commit it to version control.
• If you deploy behind a reverse proxy, ensure proper CORS and path routing so the UI can reach the MCP server endpoints.
• The UI exposes several forms (Scrape, Map, Crawl, Search, Extract, Agent). Each form maps to a corresponding MCP endpoint on the server side.
• You can override the default Firecrawl API key using the FIRECRAWL_API_KEY environment variable in the deployment environment.
• For production deployments, consider pinning Node.js to a stable LTS version and enabling proper logging and error handling in server/api.js.