WebSearch Tools MCP Server

A powerful web search and content extraction tool built with Python, leveraging the Firecrawl API for advanced web scraping, searching, and content

Local serverstdioPython

What is the WebSearch Tools MCP server?

Websearch tools mcp server lets Claude, Cursor and other MCP clients work with WebSearch Tools directly. A powerful web search and content extraction tool built with Python, leveraging the Firecrawl API for advanced web scraping, searching, and content analysis capabilities.

What WebSearch Tools does

A powerful web search and content extraction tool built with Python, leveraging the Firecrawl API for advanced web scraping, searching, and content analysis capabilities.

Tools it exposes

Once connected, the assistant can call these 5 tools directly:

  • Search — The Search tool exposed by this server
  • Extract — The Extract tool exposed by this server
  • Crawl — The Crawl tool exposed by this server
  • Scrape — The Scrape tool exposed by this server
  • Troubleshooting — 1. Ensure all required API keys are set in your .env file 2. Verify the API keys are valid and have not expired 3. Check that the .env file is in the root

Installing the websearch tools mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 2 environment variables: FIRECRAWL_API_KEY, OPENAI_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Search and scraping servers exist to fix the single most common failure of any assistant: answering from stale training data instead of what is on the web today. WebSearch Tools sits in that group, and the shape of its toolset — Search, Extract, Crawl among others — tells you what it is really for. Worth comparing against the other search web scraping servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Maintained by josemartinrodriguezmortaloni, written in Python.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the websearch tools mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
SearchThe Search tool exposed by this server.
ExtractThe Extract tool exposed by this server.
CrawlThe Crawl tool exposed by this server.
ScrapeThe Scrape tool exposed by this server.
Troubleshooting1. Ensure all required API keys are set in your .env file 2. Verify the API keys are valid and have not expired 3. Check that the .env file is in the root directory of the project 4. Make sure the environment variables a

Configuration

VariableDescriptionRequired
FIRECRAWL_API_KEYCredential the server authenticates with.Yes
OPENAI_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use WebSearch Tools to Search.
  • Use WebSearch Tools to Extract.
  • Use WebSearch Tools to Crawl.

Frequently asked questions

It connects WebSearch Tools to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (Search, Extract, Crawl, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with WebSearch Tools directly.