Fetch Browser
Fetch Browser is a headless browser server that enables access to web content and Google searches without API keys.
Key capabilities:
Fetch web content from any URL or API endpoint with error handling
Execute Google searches for web or news content
Customize search parameters including number of results (1-100)
Multiple output formats: HTML, JSON, Text, or Markdown
Automatic error handling with retries, timeouts, and rate limiting
Format conversion between HTML, Markdown, JSON, and plain text
Security features including response size limits and request timeouts
No API keys required for any operations
Enables executing Google searches and extracting structured results, supporting both web and news results with configurable output formats.
Supports conversion of web content to clean, structured Markdown format with proper formatting of lists, bold text, italic text, and links.
Provides TypeScript client integration for AI agents to fetch web content and perform Google searches programmatically.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Fetch Browser search for latest AI news and summarize in markdown"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Fetch Browser
A powerful headless browser MCP server that enables AI agents to fetch web content and perform Google searches without requiring any API keys. Built with modern web standards and designed for seamless integration with AI platforms.
Features
No API Keys Required: Uses a sophisticated headless browser approach to fetch content directly
Smart Google Search:
Extract structured results from Google searches
Support for both web and news results
Configurable number of results (1-100)
Full content fetching of search results
Automatic retry and error handling
Universal Content Fetching:
Support for any webpage or API endpoint
Multiple output formats (HTML, JSON, Text, Markdown)
Automatic content type detection
Response size limits and timeout protection
Rate limiting protection
Format Conversion:
Clean HTML to Markdown conversion
Pretty-printed JSON responses
Structured HTML output
Plain text with proper formatting
Related MCP server: Local Browser MCP
Tools
1. Google Search Tool (google_search)
Executes Google searches and fetches full content of results:
{
query: "your search query",
responseType: "markdown", // or "json", "html", "text"
maxResults: 10, // 1-100 results
topic: "web" // or "news"
}2. URL Fetcher Tool (fetch_url)
Fetches content from any URL:
{
url: "https://example.com",
responseType: "markdown", // or "json", "html", "text"
timeout: 30000 // optional, in milliseconds
}Installation
Via Smithery
# For Claude
npx -y @smithery/cli install @TheSethRose/fetch-browser --client claude
# For Cursor
npx -y @smithery/cli install @TheSethRose/fetch-browser --client cursor
# For TypeScript
npx -y @smithery/cli install @TheSethRose/fetch-browser --client typescriptManual Installation
# Clone the repository
git clone https://github.com/TheSethRose/fetch-browser.git
cd fetch-browser
# Install dependencies
npm install
# Build the project
npm run build
# Start the server
npm startDevelopment
# Watch mode with auto-rebuild
npm run watch
# Run with inspector
npm run inspector
# Debug mode
npm run debug
# Debug with watch mode
npm run debug:watchResponse Formats
1. Markdown Format
## [Page Title](https://example.com)
Content converted to clean markdown with:
- Lists
- **Bold text**
- *Italic text*
- [Links](https://example.com)2. JSON Format
{
"url": "https://example.com",
"content": "Extracted content...",
"error": null
}3. HTML Format
<div class="search-result">
<h2><a href="https://example.com">Page Title</a></h2>
<div class="content">
Original HTML content
</div>
</div>4. Text Format
### https://example.com
Plain text content with preserved formatting
==========Error Handling
Automatic retries with exponential backoff
Rate limiting protection
Timeout handling
Detailed error messages
Individual result error tracking
Security Features
Response size limits
Request timeouts
Rate limiting protection
No API keys or secrets required
Proper error handling
Credits
Created by Seth Rose:
Website: https://www.sethrose.dev
𝕏 (Twitter): https://x.com/TheSethRose
🦋 (Bluesky): https://bsky.app/profile/sethrose.dev
License
MIT License - See LICENSE for details
Available Tools
2 toolsfetch_urlC
Fetch content from a URL with proper error handling and response processing
Inputs: url (required), responseType, timeout.
google_searchC
Execute a Google search and return results in various formats
Inputs: query (required), responseType, maxResults, topic.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: fetch_url retrieves content from a specific URL, while google_search performs web searches and returns results. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the task.
Both tools follow a verb_noun pattern (fetch_url, google_search), which is consistent and predictable. The minor deviation is that google_search includes a brand name, but this does not break the overall naming convention.
With only 2 tools, the server feels thin for a browser-related purpose, as it lacks common operations like navigating pages, handling cookies, or interacting with web elements. However, the tools provided are core functionalities, so it's borderline appropriate.
For a browser server, there are significant gaps in coverage, such as no tools for page navigation, form submission, JavaScript execution, or session management. The surface is severely incomplete for typical browser automation tasks, limiting agent effectiveness.
Maintenance
Related MCP Connectors
Web search API and MCP server for developers building AI agents.
Web scraping, browser automation, screenshots and AI data extraction for AI agents via MCP.
Official Browserless MCP server: browser automation, scraping, screenshots and PDFs for AI agents.
Free web search for AI agents. No API key required. Hosted MCP in active development.
Related MCP Servers
- AlicenseAqualityBmaintenanceAn MCP server that enables AI assistants to fetch web content in multiple formats (HTML, JSON, text, Markdown) with intelligent content extraction, chunk management, and browser automation support.6152 npm15MIT
- AlicenseBqualityBmaintenanceA headless, agent-controllable real browser as an MCP server that enables AI agents to navigate, click, fill, eval JavaScript, and take screenshots on localhost and allowed hosts, with no GUI required.277MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for web scraping and browser automation, enabling AI agents to extract clean, token-efficient content from web pages.1MIT

Wickofficial
FlicenseNot gradedqualityCmaintenanceAn MCP server that provides browser-grade web access for AI agents, using Chrome's actual network stack to bypass anti-bot protections and return clean markdown.9-