mcp-agno
Related Servers
Alternatives to mcp-agno
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides access to Agno framework documentation for AI agents, enabling search and retrieval of SDK references, API endpoints, code examples, and integration guides through MCP-compatible tools.73MIT
- FlicenseNot gradedqualityAmaintenanceThis MCP server enables AI clients to search and retrieve current technical documentation for supported agent frameworks over stdio or SSE.-
- FlicenseNot gradedqualityAmaintenanceThis MCP server enables AI clients to search and retrieve up-to-date technical documentation for supported agent frameworks, including LangChain, LlamaIndex, AutoGen, Agno, OpenAI Agents SDK, MCP docs, Camel AI, and CrewAI. It supports both stdio and SSE transports.-
- FlicenseNot gradedqualityDmaintenanceMCP server that exposes one or more documentation folders (Markdown, MDX, TXT) to AI agents, enabling listing, reading, and searching of documentation files.-
- FlicenseNot gradedqualityAmaintenanceEnables AI clients to search and retrieve current technical documentation for supported agent frameworks such as LangChain, LlamaIndex, AutoGen, Agno, OpenAI Agents SDK, MCP docs, CAMEL-AI, and CrewAI. It supports both stdio and SSE transport so documentation can be accessed locally or remotely.-
- FlicenseNot gradedqualityCmaintenanceAn MCP server that serves company documentation from a Markdown folder, exposing read-only search and fetch tools for agents to discover and retrieve authoritative documents.-
TDQS
Scored across 3 tools
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.