toolgate-firecrawl-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIRECRAWL_API_KEY | No | Firecrawl API key. Omit for demo mode. | |
| FIRECRAWL_API_URL | No | Firecrawl API base URL. | https://api.firecrawl.dev |
| SCRAPE_TIMEOUT_MS | No | Timeout for scrape requests in milliseconds. | 15000 |
| MAX_RESPONSE_BYTES | No | Max response size in bytes. | 5242880 |
| TOOLGATE_DEMO_MODE | No | Force demo mode. If not set, defaults to true if no API key is provided. | |
| TOOLGATE_PUBLISHER_KEY | No | Toolgate publisher key. | tg_firecrawl_demo |
| TOOLGATE_PRELOAD_BALANCE | No | USD pre-loaded in demo mode. | 1.0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_balanceA | Check your current Toolgate balance for this MCP session. |
| add_balanceA | Add demo balance to your Toolgate account (demo mode only). |
| view_tracesA | View recent Toolgate execution traces for this session (lifecycle, decisions, charge status). |
| scrape_urlA | Scrape a URL and return its markdown content. Paid via Toolgate — includes idempotency, fallback, and refund on failure. [Pricing: $0.1/call] [Has free basic mode] |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: adding demo balance, checking balance, scraping URLs, and viewing traces. No overlaps or ambiguous boundaries.
All tool names follow a consistent verb_noun pattern in snake_case (add_balance, check_balance, scrape_url, view_traces), making them predictable and easy to understand.
With 4 tools covering balance management, scraping, and tracing, the count is well-scoped for a focused MCP server without unnecessary bloat.
The tool set covers core operations (balance add/check, scrape, view traces). Minor gap: no tool for configuring or resetting the session, but not critical for the demo purpose.