Add Firecrawl monitor tools (#234)

* Add Firecrawl monitor tools

Introduce a new monitor tools module (src/monitor.ts) and register it from src/index.ts. The module implements direct /v2/monitor HTTP calls (monitorRequest) — including auth resolution and query handling — to work around the SDK's injected `origin` field that breaks monitor endpoints. It registers several MCP tools for monitors (create, list, get, update, delete, run, checks, check) that serialize responses as JSON text. Also adds the import and registerMonitorTools(server) call before server.start.

* Update monitor.ts

* Update package.json

* Nick:

---------

Co-authored-by: Nicolas <20311743+nickscamara@users.noreply.github.com>

Author: developersdigest

package.json

@@ -1,6 +1,6 @@
 {
   "name": "firecrawl-mcp",
-  "version": "3.16.0",
+  "version": "3.17.0",
   "description": "MCP server for Firecrawl — search, scrape, and interact with the web. Supports both cloud and self-hosted instances. Features include web search, scraping, page interaction, batch processing, and LLM-powered content analysis.",
   "type": "module",
   "mcpName": "io.github.firecrawl/firecrawl-mcp-server",
@@ -28,7 +28,7 @@
   },
   "license": "MIT",
   "dependencies": {
-    "@mendable/firecrawl-js": "4.21.0",
+    "@mendable/firecrawl-js": "4.24.0",
     "dotenv": "^17.2.2",
     "firecrawl-fastmcp": "^1.0.4",
     "typescript": "^5.9.2",

pnpm-lock.yaml

@@ -6,6 +6,7 @@ import FirecrawlApp from '@mendable/firecrawl-js';
 import type { IncomingHttpHeaders } from 'http';
 import { readFile } from 'node:fs/promises';
 import path from 'node:path';
+import { registerMonitorTools } from './monitor.js';
 
 dotenv.config({ debug: false, quiet: true });
 
@@ -1853,4 +1854,6 @@ if (
   };
 }
 
+registerMonitorTools(server);
+
 await server.start(args);