ollama-web-tools-mcp
Provides web search and web fetch tools, using Ollama as the backend service for API authentication and request handling.
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., "@ollama-web-tools-mcp Search the web for Ollama Web Tools MCP setup guide"
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.
Ollama Web Tools MCP
Python 3.12+ MCP server preserving the Ruby oracle's web_search and web_fetch
contracts and adding cluesift_domain_fetch. It uses the official Python MCP SDK,
stdio by default, and stateless JSON streamable HTTP at / with --http.
Configuration
Production (prod or production in the first set of ENVIRONMENT,
CLUESIFT_ENV, or ENV) requires OLLAMA_KEY_POOL_FILE. The reloadable UTF-8
JSON document has exactly this useful shape; array order is strict priority and
duplicates are removed while preserving first occurrence:
{"keys":["primary-ollama-tools-key","secondary-ollama-tools-key"]}The file is re-read when its mtime changes or after a two-second TTL. Outside
production only, comma-separated OLLAMA_CLOUD_API_KEYS, then OLLAMA_API_KEY,
are fallback inputs. Keys are never logged; diagnostics identify them only by the
first 12 lowercase hex characters of SHA-256.
Optional Ollama timeouts: OLLAMA_OPEN_TIMEOUT=10, OLLAMA_READ_TIMEOUT=60,
OLLAMA_WRITE_TIMEOUT=30. ClueSift aliases use complete endpoint URLs (not base
URLs):
cluesift-test:CLUESIFT_ARTIFACT_TEST_URLand_TOKENcluesift-prod:CLUESIFT_ARTIFACT_PROD_URLand_TOKEN
Each pair must be wholly present or absent. Callback timeout defaults are
CLUESIFT_ARTIFACT_OPEN_TIMEOUT=2, ...READ_TIMEOUT=5, and
...WRITE_TIMEOUT=5. Callback failures are content-free telemetry and never
replace a successful fetch result.
Callback URLs are complete absolute HTTP(S) endpoints, may use only their
scheme's default port, and may not contain userinfo, a query, or a fragment.
Fetched public URLs reject trailing-dot hosts rather than canonicalizing them.
Related MCP server: web-mcp-server
Run and develop
python -m venv .venv
.venv/bin/pip install -e '.[dev]'
.venv/bin/ollama-web-tools-mcp
.venv/bin/ollama-web-tools-mcp --http --port 8767
.venv/bin/ruff check .
.venv/bin/ruff format --check .
.venv/bin/pytestThe three tools are exactly web_search, web_fetch, and
cluesift_domain_fetch. The ClueSift tool accepts only url, artifact_target,
request_id, and case_id; see the copied implementation brief for its full
security and delivery contract.
Available Tools
3 toolscluesift_domain_fetchC
Fetch a public page and best-effort deliver it to a fixed ClueSift target.
Inputs: url (required), case_id (required), request_id (required), artifact_target (required).
web_fetchC
Fetch web page content using Ollama's web fetch API.
Inputs: url (required), truncate, max_chars.
web_searchC
Search the internet using Ollama's web search API.
Inputs: query (required), truncate, max_chars, max_results.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
web_search clearly differs from the fetch tools. web_fetch and cluesift_domain_fetch both fetch pages, but cluesift_domain_fetch has a distinct delivery target, reducing confusion. One or two could be confused but descriptions clarify.
web_search and web_fetch follow a consistent noun-verb pattern. cluesift_domain_fetch deviates by adding a longer domain prefix, but still ends with a verb and uses consistent snake_case.
3 tools is on the lower end but appropriate for a focused web search/fetch server; each tool has a clear purpose, though the server may seem slightly thin.
The core web operations of search and fetch are covered, plus a specialized fetch-to-target. Minor gaps exist (e.g., no tool for parsing or summarizing pages) but not critical for the primary use case.
Related MCP Connectors
Web search API and MCP server for developers building AI agents.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Docs: https://docs.keenable.ai/mcp-server Keenable is a free, remote MCP server that gives agents access to the web index. Search the web with ranked results and date/site filters, then fetch any indexed page as clean markdown. Works out of the box with no account or API key.
Related MCP Servers
- AlicenseBqualityDmaintenanceA local MCP server that exposes Tavily search as a tool and rotates across multiple API keys for reliability.1MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes web_search and web_fetch tools, allowing LLM applications to search the web via DuckDuckGo and fetch page content as cleaned markdown.-
- AlicenseNot gradedqualityCmaintenanceA self-contained web-research MCP server that lets local LLM agents search, fetch, and synthesize web content using tools like web_search, web_fetch, and web_research.2MIT
- AlicenseNot gradedqualityDmaintenanceA modular MCP server that provides file search, URL fetching, text reading, knowledge base search, and image embedding tools, with a web interface powered by an Ollama agent.MIT