Developer · Local MCP server
webfetch
Self-hosted web search for LLM agents: search -> fetch -> rank pipeline with semantic caching.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.firish/webfetch- Version
- 0.1.3
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-07-19
- Updated
- 2026-07-19
- Publisher
- firish (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/firish) · how
- Repository
- github.com/firish/webfetch
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | webfetch-llm | 0.1.3 | stdio |
How to connect webfetch
webfetch runs locally from a Python package published to PyPI: webfetch-llm version 0.1.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx webfetch-llm. It reads these environment variables: BRAVE_API_KEY (secret), SERPER_API_KEY (secret), TAVILY_API_KEY (secret) and WEBFETCH_PROVIDER; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"webfetch": {
"command": "uvx",
"args": [
"webfetch-llm"
],
"env": {
"BRAVE_API_KEY": "<secret>",
"SERPER_API_KEY": "<secret>",
"TAVILY_API_KEY": "<secret>",
"WEBFETCH_PROVIDER": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Webcomponents React MCP ServerMCP server for UI5 Web Components for React - Developer documentation and API assistance. | Local · stdio, HTTP |
| WebDAV MCPZero-dependency WebDAV MCP server - single static binary, no Node.js or Python. 8 tools via stdio. | Local · stdio |
| webdriverio MCPMCP server with WebdriverIO for browser and mobile app automation (iOS/Android via Appium) | Local · stdio |
| webEmbeddingSource-first URL clone, capture, rebuild, and fidelity verification tools. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| Webhook AdminSend, retry and monitor webhooks: manage endpoints, event types and API keys (OAuth). | Remote · HTTPLive check: sign-in required |
| Webhook Ai MCPWebhook Ai tools for AI agents. Capabilities: validate webhook signature, log webhook event, replay. | Local · stdio |
| Webhook Signature Fixture LabGenerates deterministic webhook HMAC-SHA256 fixtures and optionally verifies a supplied signature... | Remote · HTTPLive check: ✓ handshake |
| Webhook StudioKeyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic. | Remote · HTTPLive check: ✓ handshake |