Skip to main content
Glama
Attilio81

mcp-agno

by Attilio81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-agno

No user-submitted related servers found.

    Related Servers

    • docs-mcp-server

      DewminK
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes one or more documentation folders (Markdown, MDX, TXT) to AI agents, enabling listing, reading, and searching of documentation files.
      -

    • skill-mcp

      jacobragsdale
      F
      license
      Not graded
      quality
      C
      maintenance
      An 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.
      -

    • devdoc

      vision-release
      A
      license
      Not graded
      quality
      C
      maintenance
      A documentation MCP server that crawls websites and Git repositories, stores them as Markdown, and provides tools to search and retrieve documentation for local LLMs and AI agents.
      Apache 2.0

    • mcp-docs

      gmantovani2005
      A
      license
      Not graded
      quality
      D
      maintenance
      Generic MCP server that exposes Markdown documentation to LLMs, enabling them to search and answer questions about any software documentation.
      MIT

    • Synapse

      gabriel-romero-poza
      A
      license
      Not graded
      quality
      D
      maintenance
      A project-agnostic MCP server that exposes Markdown documentation from a project's /docs folder as MCP resources for AI agents. It provides stable, up-to-date context to reduce hallucinations and ensure agents remain aligned with project-specific conventions and goals.
      6 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources