Agno MCP Search
Provides real-time web search capabilities via the Serper API, enabling the agent to fetch up-to-date information from Google Search.
Leverages Google Gemini for reasoning and answer synthesis, processing search results to generate coherent, markdown-formatted responses.
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., "@Agno MCP SearchWhat is the latest news on quantum computing?"
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.
Agno MCP Search
An MCP server that exposes an Agno agent with Google Gemini reasoning and Serper web search — usable from Claude Desktop, Cursor, or any MCP-compatible client, plus a local Streamlit UI for testing.
Overview
Modern chat assistants like Claude and ChatGPT are powerful, but their knowledge is frozen at training time. This project bridges that gap by giving them a fresh, agent-driven search capability — delivered through the Model Context Protocol (MCP).
The MCP server exposes a single tool, search(query). Behind the tool sits an Agno agent that:
Receives a natural-language query,
Uses Serper to run a Google Search,
Reasons over the top results with Google Gemini,
Returns a markdown-formatted summary to the calling MCP client.
The same server is also drivable from a local Streamlit UI, which is handy for demos and debugging without needing an MCP client running.
Related MCP server: perplexity-sonar-mcp
Why this project exists
Learn MCP by building it. MCP is quickly becoming the de-facto standard for tool-augmented LLM apps. A small, honest reference server is more useful than a giant framework demo.
Prove the agent-in-tool pattern. Rather than exposing raw search results, the tool exposes an agent. The client asks a question; the server does the retrieval-and-reason loop and returns a synthesized answer.
Stay swappable. Gemini, Serper, and Agno are all replaceable by design — the boundary is the
searchMCP tool, not the LLM or search vendor.
Architecture
flowchart LR
subgraph Client["MCP Client (Claude Desktop / Cursor / Streamlit UI)"]
UI[User query]
end
subgraph Server["FastMCP Server (agentic_mcp.server)"]
TOOL["search(query)"]
AGENT[Agno Agent]
GEMINI[[Gemini LLM]]
SERPER[[Serper Search]]
end
UI -- MCP call --> TOOL
TOOL --> AGENT
AGENT -- reasoning --> GEMINI
AGENT -- tool use --> SERPER
SERPER -- results --> AGENT
GEMINI -- answer --> AGENT
AGENT -- markdown --> TOOL
TOOL -- MCP response --> UITechnology stack
Layer | Library / Service | Purpose |
Protocol | FastMCP | MCP server framework — exposes tools over stdio |
Agent framework | Agno | Agent loop, tool orchestration, markdown formatting |
LLM | Google Gemini | Reasoning and answer synthesis |
Search | Serper | Google Search API |
Local UI | Streamlit | Browser-based demo client |
Config | python-dotenv | Loads secrets from |
Test / lint | pytest, ruff | Test runner and linter |
Folder structure
agno-mcp-search/
├── agentic_mcp/ # Application package
│ ├── __init__.py
│ ├── config.py # Env loading & validation
│ ├── agent.py # Agno agent factory
│ ├── server.py # FastMCP server + search tool
│ └── ui/
│ └── streamlit_app.py # Streamlit demo UI
├── tests/ # pytest suite
│ ├── test_config.py
│ └── test_server.py
├── scripts/
│ └── verify_env.py # One-shot health checks
├── docs/
│ ├── Architecture.md
│ ├── MCP.md
│ └── Installation.md
├── screenshots/ # (add your captures here)
├── .github/workflows/ci.yml # Lint + test on every PR
├── .env.example
├── .gitignore
├── LICENSE # MIT
├── README.md
├── CONTRIBUTING.md
├── CODE_OF_CONDUCT.md
├── SECURITY.md
├── CHANGELOG.md
├── pyproject.toml # Modern packaging + tool config
├── requirements.txt
└── requirements-dev.txtInstallation
Prerequisites
Python 3.10+
Optional: uv for faster installs
Setup with pip
# 1. Clone
git clone https://github.com/kishansri/agno-mcp-search.git
cd agno-mcp-search
# 2. Create a venv
python -m venv venv
source venv/bin/activate # macOS/Linux
venv\Scripts\Activate.ps1 # Windows PowerShell
# 3. Install (dev mode)
pip install -e ".[dev]"
# 4. Configure secrets
cp .env.example .env # macOS/Linux
Copy-Item .env.example .env # Windows PowerShell
# then edit .env and paste your keysSetup with uv
git clone https://github.com/kishansri/agno-mcp-search.git
cd agno-mcp-search
uv venv
uv pip install -e ".[dev]"
cp .env.example .envEnvironment variables
Variable | Required | Default | Purpose |
| Yes | — | Gemini access |
| Yes | — | Serper Google Search |
| No |
| Override the default Gemini model |
| No |
| Log verbosity written to |
Running
1. Verify your setup
python scripts/verify_env.py allThis runs env, Gemini, Serper, and end-to-end Agno checks. It never prints your keys.
2. Run the MCP server
python -m agentic_mcp.server
# or, if installed via pip:
agentic-mcp3. Run the Streamlit UI
streamlit run agentic_mcp/ui/streamlit_app.pyOpen http://localhost:8501 and enter a query.
4. Install into Claude Desktop
fastmcp install claude-desktop agentic_mcp/server.py \
--with agno --with google-genai --with fastmcp --with python-dotenv \
--env-file .envRestart Claude Desktop. The search tool will appear in the tool picker.
How the agent works
Tool receives a query.
search(query: str)is invoked by the MCP client.Input is validated. Empty or overly long queries are rejected before spending API credits.
Agent runs the reasoning loop. Agno decides when to call Serper and how many times.
Gemini synthesizes the answer. Search snippets are handed to Gemini for summarization.
Result is returned as markdown. The MCP client renders it as-is.
Features
✅ Single-tool MCP server (
search)✅ Agno agent with Gemini reasoning + Serper search
✅ Streamlit local UI
✅ Fail-fast config validation
✅ Logging to file (stdout stays clean for MCP protocol)
✅ pytest suite with mocked external calls
✅ CI-ready (
.github/workflows/ci.yml)
Known limitations
Single-agent design. No multi-agent planner/reviewer split (yet — see roadmap).
No caching. Repeated queries re-hit Gemini and Serper.
No RAG or memory. Every query is stateless.
No auth on the MCP tool. Fine for local use; do not expose over the network without adding auth.
Preview models may break. If you set
GEMINI_MODEL_IDto a preview alias and Google deprecates it, the tool will fail until you change the env var.
Roadmap
See CHANGELOG.md for released versions and docs/Architecture.md for planned multi-agent design.
Short version:
v0.2 — Response caching, richer tool description, structured JSON output option.
v0.3 — Optional Planner + Researcher + Reviewer multi-agent flow.
v1.0 — Docker image, CI/CD, guardrails, observability.
Contributing
Contributions welcome. See CONTRIBUTING.md.
Security
Please read SECURITY.md before reporting vulnerabilities.
License
MIT — see LICENSE.
Screenshots
Screenshots live in screenshots/. Suggested captures:
Streamlit UI with a sample query and response
Claude Desktop showing the
searchtool availableTerminal running
verify_env.py allwith all green checks
Built with FastMCP · Agno · Gemini · Serper.
Available Tools
1 toolsearchSearchA
Search the web via Serper (Google Search API) and summarize results.
The Agno agent decides how to use the Serper tool, retrieves relevant pages, and returns a markdown-formatted answer generated by Gemini.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | A natural-language search query. Example: "latest results from the ICC Women's Cricket World Cup 2025 final". |
Output Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool uses Serper, retrieves pages, and returns a markdown answer from Gemini, which is useful. However, it does not mention any potential side effects, rate limits, costs, or whether the operation is read-only. For a search tool this is adequate but not exhaustive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, both contributing value. The first sentence states the core purpose, and the second clarifies the output format and the agent's role, which prevents misinterpretation. It is concise and front-loaded, though the second sentence could be slightly tighter.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the search process, the output format, and the agent's involvement. An output schema exists (though not shown), so return-value details are presumably documented there. The main missing piece is guidance on when to use this tool versus alternatives, but no alternatives exist. Overall, it is sufficiently complete for an agent to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single parameter, and the schema already explains the query as a natural-language search query. The description adds no additional semantics beyond what the schema provides, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific verb ('Search the web via Serper') and resource ('Google Search API'), and it describes the output (a markdown-formatted answer). It is unambiguous and would distinguish itself from any sibling even if one existed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for web searches and summarization, and it describes the internal process (agent decides, retrieves pages, returns answer). It lacks explicit when-not-to-use guidance, but since there are no sibling tools, that is not a significant gap. The context is clear enough for an agent to know when to invoke it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v0.1.0- First observed
search
TDQS
Scored across 1 tool
Only one tool exists, so there is zero risk of confusing it with another. Its purpose is clearly distinct by definition.
With a single tool named 'search', there is no opportunity for inconsistent naming patterns. The verb form is clear and matches the server's stated purpose.
The server exposes one tool, which is slightly thin but reasonable for a narrowly-scoped search utility. The tool handles both searching and summarizing, so the count is not underserved.
The domain is web search and result summarization, and the single tool covers that workflow end-to-end. There may be missing advanced options like pagination or filters, but no obvious critical gaps for the stated purpose.
Maintenance
Related MCP Connectors
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.
Your agent needs the open web — searched by more than one engine, and read as clean markdown rather than raw HTML. **What you can ask for** • "Search this question with two providers and tell me where they disagree." • "Scrape these 40 URLs into markdown, in one batch." • "Crawl this documentation site and give me every page." • "Do deep research on this topic and cite the sources." • "Find the academic papers behind this claim." **How to use it** Point any MCP client at https://mcp.aisa.one/search/mcp and sign in with OAuth — there is no key to create or paste. 30 tools across several independent providers: Tavily and Exa search, answers, contents and agent runs; Firecrawl scrape, batch scrape, crawl, map and search; Perplexity Sonar, Sonar Pro, reasoning and deep research; Oxylabs AI search and LLM jobs; OpenAI and Anthropic web search; and scholarly search. **Why this rather than the source** Several independent indexes behind one account, because one engine's blind spot is not visible from inside it. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the page here, then ask the same agent who links to it or how much traffic it gets — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo-serp/mcp for the Google results page itself, https://mcp.aisa.one/seo-serp-other-engines/mcp for Bing, Baidu and Naver.
Scrape, crawl and search the web for AI agents via MCP.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn MCP server that enables AI models to perform Google Web searches using the Gemini API, complete with citations and grounding metadata for accurate information retrieval. It is compatible with Claude Desktop and other MCP clients for real-time web access.13Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that brings Perplexity's Sonar models with real-time web search capabilities to Claude Desktop and other MCP clients.16 npm9MIT
- AlicenseAqualityDmaintenanceMCP server that bridges OpenAI's Agents SDK with Claude Code, enabling web search, file search, and computer use capabilities directly in your development environment.29 npm1MIT
- AlicenseAqualityFmaintenanceMCP server for web search powered by Google AI Mode (Gemini). Enables any AI agent to search the web in real-time for free and without rate limits.2182MIT