Click on "Install 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., "@mcp-agno How do I build a multi-agent team with Agno?"
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.
An MCP (Model Context Protocol) server that gives AI assistants direct access to the AGNO framework documentation.
Instead of crawling docs manually or relying on outdated training data, Claude and other MCP-compatible clients can browse, fetch, and search AGNO docs in real time.
Exposes three MCP tools:
Tool | Description |
| List all available documentation sections with their slugs and URLs |
| Fetch the full content of a documentation page by slug or URL |
| Keyword search across the catalog — returns matching slugs without fetching pages |
On startup the server seeds a catalog of core sections (Introduction, Agents, Teams, Workflows, AgentOS) and auto-discovers additional pages from the live AGNO sitemap.
Related MCP server: mcp-docs
Python 3.11+
uv (recommended) or pip
git clone https://github.com/Attilio81/MCP_AGNO.git
cd MCP_AGNO
uv pip install -e .git clone https://github.com/Attilio81/MCP_AGNO.git
cd MCP_AGNO
pip install -e .This installs the mcp-agno command.
Add the server to your Claude Desktop config (claude_desktop_config.json):
{
"mcpServers": {
"agno-docs": {
"command": "mcp-agno"
}
}
}If you installed with uv in a virtual environment, use the full path:
{
"mcpServers": {
"agno-docs": {
"command": "/path/to/venv/bin/mcp-agno"
}
}
}Restart Claude Desktop. The three tools will appear automatically.
claude mcp add agno-docs mcp-agnoOr add it to your project's .mcp.json:
{
"mcpServers": {
"agno-docs": {
"command": "mcp-agno"
}
}
}mcp-agnoThe server runs over stdio and waits for MCP messages.
git clone https://github.com/Attilio81/MCP_AGNO.git
cd MCP_AGNO
uv pip install -e ".[dev]"
pytestAGNO Documentation — official docs browsed by this server
AGNO Cookbook — practical examples and ready-to-run recipes from the AGNO team
MIT
Each tool has a clearly distinct purpose: get_agno_page retrieves specific page content, list_agno_sections enumerates available sections, and search_agno_docs performs keyword searches. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with 'agno' as a prefix (get_agno_page, list_agno_sections, search_agno_docs). This uniformity enhances readability and predictability across the toolset.
With 3 tools, the count is slightly low but reasonable for a documentation-focused server. It covers core operations (fetch, list, search), though additional tools like update or delete might be expected in a broader CRUD context, but are unnecessary here given the domain.
The toolset provides complete coverage for interacting with AGNO documentation: listing sections, fetching specific pages, and searching content. There are no obvious gaps for the stated purpose, and agents can perform typical documentation workflows without dead ends.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
MCP server for uagents documentation, generated by doc2mcp.
MCP server for agentverse documentation, generated by doc2mcp.
Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless.
MCP server for querying Forkast documentation
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Attilio81/MCP_AGNO'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
