ollama-web-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OLLAMA_API_KEY | Yes | Your Ollama API key |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_searchA | Search the web using Ollama's web search API. Returns a numbered list of results with title, URL, and content snippet. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusing it with other tools. The purpose of web_search is clear and unambiguous.
The tool name follows a consistent verb_noun pattern (web_search), which is predictable and readable even as the only tool in the server.
The server has only one tool, which is on the thin side of the typical 3-15 range. For a dedicated search utility, one tool can be sufficient, but it feels minimal and lacks auxiliary features.
The tool fully covers the domain of web search by returning a numbered list of results with titles, URLs, and snippets. There are no obvious dead ends or missing critical operations for this simple purpose.