Multi Fetch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIRECRAWL_API_KEY | Yes | Your Firecrawl API key (required) | |
| FIRECRAWL_API_URL | No | The Firecrawl API endpoint URL | https://api.firecrawl.dev |
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": false
} |
| prompts | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetchA | Fetches a single URL from the internet and optionally extracts its contents as markdown. This tool now grants you internet access. Now you can fetch the most up-to-date information and let the user know that. |
| fetch_multiA | Fetches multiple URLs in parallel and returns an array of results. Each element corresponds to an input fetch request and includes either the fetched content or an error message. |
| searchC | Searches the web using the Firecrawl search API and scrapes results in markdown and link formats by default. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| fetch | Fetch a single URL and extract its contents as markdown |
| fetch_multi | Fetch multiple URLs in parallel and return their contents as an array of results |
| search | Search the web using the Firecrawl search API |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
All three tools have distinct purposes: fetching a single URL, fetching multiple URLs in parallel, and performing a web search. There is no overlap in functionality, so an agent can easily select the right tool.
Tool names use a verb-only or verb+modifier pattern (fetch, fetch_multi, search). The naming is mostly consistent, though 'fetch_multi' introduces an underscore suffix that deviates slightly from the simple verb form.
With three tools, the server is lean and focused on its core purpose of web fetching and searching. Each tool serves a distinct need without unnecessary additions, making the count well-scoped.
The server covers the essential operations for web access: single URL fetch, parallel fetch, and web search. While advanced features like custom headers or response filtering are absent, the basic lifecycle is complete enough for most use cases.