Skip to main content
Glama

Agno Docs MCP Server

A Model Context Protocol (MCP) server that provides access to Agno framework documentation. Enables developers to easily access Agno docs through coding agents like Claude Code, Cursor, and other MCP-compatible tools.

Quick Start (New Laptop Setup)

Prerequisites

  • Python 3.10 or higher

  • Git

  • Access to the agno-docs repository (for documentation source)

Step 1: Clone the Repository

git clone https://github.com/agno-agi/agno-docs-mcp
cd agno-docs-mcp

Step 2: Create Virtual Environment

python3 -m venv .venv
source .venv/bin/activate  # On Windows: .venv\Scripts\activate

Step 3: Install Dependencies

# Upgrade pip first (required for pyproject.toml editable installs)
pip install --upgrade pip

# Install the package in editable mode with dev dependencies
pip install -e ".[dev]"

Step 4: Clone Agno Docs (if not already available)

# Clone the agno-docs repository (adjust path as needed)
git clone https://github.com/agno-agi/agno-docs ~/Work/agno-docs

Step 5: Prepare Documentation

# Set the path to your agno-docs repository
export AGNO_DOCS_PATH=~/Work/agno-docs

# Run the preparation script to copy and index docs
python -m agno_docs_mcp.prepare

You should see output like:

Preparing Agno documentation...
  Source: /Users/you/Work/agno-docs
  Output: /Users/you/Work/agno-docs-mcp/.docs

Copying documentation files...
  Copied 596 files from basics/
  Copied 148 files from reference/
  Copied 74 files from reference-api/
  ...
  Copied OpenAPI spec (openapi.json)

Building search index...
  Indexed 1851 files in 10 categories

Done!

Step 6: Configure Your MCP Client

Claude Code

Add to ~/.claude.json or your project's .claude/settings.json:

{
  "mcpServers": {
    "agno-docs": {
      "command": "/path/to/agno-docs-mcp/.venv/bin/python",
      "args": ["-m", "agno_docs_mcp"]
    }
  }
}

Cursor

Add to your Cursor MCP settings (.cursor/mcp.json):

{
  "mcpServers": {
    "agno-docs": {
      "command": "/path/to/agno-docs-mcp/.venv/bin/python",
      "args": ["-m", "agno_docs_mcp"]
    }
  }
}

Using HTTP Transport (Remote Access)

{
  "mcpServers": {
    "agno-docs": {
      "url": "http://localhost:8000/mcp",
      "transport": "streamable-http"
    }
  }
}

Step 7: Verify Installation

# Test the server directly
python -c "from agno_docs_mcp.tools.api import agno_api; print(agno_api('memory')[:200])"

# Or start the HTTP server
python -m agno_docs_mcp --transport http --port 8000

# In another terminal, test with curl
curl -X POST http://localhost:8000/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Related MCP server: MCP Framework Documentation Server

Features

  • 7 Specialized Tools for navigating Agno documentation:

    • agno_docs - SDK conceptual documentation (agents, teams, workflows, basics)

    • agno_reference - SDK class and method reference

    • agno_examples - Code snippets and usage examples

    • agno_integrations - Database, VectorDB, and model provider guides

    • agno_agentos - AgentOS runtime documentation

    • agno_api - REST API endpoints from OpenAPI spec

    • agno_migration - Migration guides, FAQs, and troubleshooting

  • OpenAPI Integration - Parses the OpenAPI spec for accurate REST endpoint docs

  • Keyword-based search across all documentation

  • Path-based navigation for exploring docs structure

  • Offline support - docs are preprocessed and bundled locally

  • Multiple transports - stdio (local) and HTTP (remote) support

Running the Server

Local CLI Mode (stdio) - Default

# Activate venv first
source .venv/bin/activate

# Run with stdio transport (for Claude Code, Cursor)
python -m agno_docs_mcp

HTTP Server Mode

# Run HTTP server on port 8000
python -m agno_docs_mcp --transport http --port 8000

# Server available at http://localhost:8000/mcp
# Health check at http://localhost:8000/health

Production Deployment

# Using uvicorn directly
uvicorn agno_docs_mcp.app:app --host 0.0.0.0 --port 8000

# Using Docker
docker build -t agno-docs-mcp .
docker run -p 8000:8000 agno-docs-mcp

Tools Reference

agno_api (NEW - REST API Endpoints)

Get AgentOS REST API endpoints from the OpenAPI specification.

agno_api(resource="memory")

Parameters:

  • resource (str) - API resource: memory, agents, teams, workflows, sessions, knowledge, evals, traces, metrics, database, playground

Use for: REST API endpoints, HTTP methods, request/response schemas

agno_docs

Get SDK conceptual documentation and guides for writing agent code.

agno_docs(path="basics/agents/")

Parameters:

  • path (str) - Documentation path (e.g., "basics/", "basics/agents/", "basics/memory/")

Use for: How to write Python code with Agno SDK

agno_reference

Get SDK class and method reference (parameters, signatures, options).

agno_reference(topic="agents")

Parameters:

  • topic (str) - Reference topic: agents, teams, workflows, tools, models, memory, knowledge, storage, hooks, compression, reasoning, agent-os

Use for: Agent() constructor parameters, method signatures, configuration options

agno_examples

Get SDK code examples for building agents.

agno_examples(category="agents")

Parameters:

  • category (str) - Category: agents, teams, workflows, tools, memory, knowledge, models, database, evals, guardrails, hitl, multimodal, reasoning, sessions, tracing

agno_integrations

Get integration documentation for databases, vector stores, and models.

agno_integrations(integration_type="database", name="postgres")

Parameters:

  • integration_type (str) - Type: database, vectordb, models, toolkits

  • name (str, optional) - Specific integration name

agno_agentos

Get AgentOS runtime and deployment documentation.

agno_agentos(path="features/memories")

Parameters:

  • path (str) - Path within AgentOS docs (e.g., "api/", "features/", "security/")

Use for: Deployment docs, runtime features, authentication, middleware

agno_migration

Get migration guides and FAQ documentation.

agno_migration(topic="v2-migration")

Parameters:

  • topic (str) - Migration topic or FAQ topic

Tool Selection Guide

Question Type

Use This Tool

"What REST API endpoints for memory?"

agno_api("memory")

"How to create an agent in Python?"

agno_docs("basics/agents/")

"What parameters does Agent() accept?"

agno_reference("agents")

"Show me agent code examples"

agno_examples("agents")

"How to connect to Postgres?"

agno_integrations("database", "postgres")

"How to deploy agents?"

agno_agentos("api/")

"How to migrate from v1?"

agno_migration("v2-migration")

Project Structure

agno-docs-mcp/
├── pyproject.toml
├── README.md
├── .venv/                      # Virtual environment
├── src/
│   └── agno_docs_mcp/
│       ├── __init__.py
│       ├── __main__.py
│       ├── server.py           # Main MCP server with tool registration
│       ├── app.py              # FastAPI/ASGI app for HTTP
│       ├── tools/              # Tool implementations
│       │   ├── docs.py
│       │   ├── reference.py
│       │   ├── examples.py
│       │   ├── integrations.py
│       │   ├── agentos.py
│       │   ├── api.py          # NEW: OpenAPI parser
│       │   └── migration.py
│       ├── utils/              # Utility modules
│       │   ├── search.py
│       │   ├── paths.py
│       │   └── content.py
│       └── prepare/            # Doc preparation
│           └── prepare_docs.py
├── .docs/                      # Preprocessed docs (generated)
│   ├── raw/                    # Copied MDX files
│   ├── snippets/               # Snippet files
│   ├── index.json              # Search index
│   └── openapi.json            # OpenAPI spec
└── tests/

Updating Documentation

When the agno-docs repository is updated:

# Pull latest docs
cd ~/Work/agno-docs
git pull

# Re-run preparation
cd ~/Work/agno-docs-mcp
source .venv/bin/activate
python -m agno_docs_mcp.prepare

Troubleshooting

"OpenAPI specification not found"

Run the prepare script:

export AGNO_DOCS_PATH=~/Work/agno-docs
python -m agno_docs_mcp.prepare

"Module not found" errors

Make sure you're using the virtual environment:

source .venv/bin/activate
which python  # Should show .venv/bin/python

MCP client not connecting

  1. Check the path in your MCP config points to the venv Python:

    "command": "/absolute/path/to/agno-docs-mcp/.venv/bin/python"
  2. Test the server manually:

    /path/to/agno-docs-mcp/.venv/bin/python -m agno_docs_mcp

License

MIT

Available Tools

7 tools
agno_agentosA

Get AgentOS runtime and deployment documentation (REST APIs, endpoints, hosting).

Args: path: Path within AgentOS docs. Leave empty for overview.

AgentOS Sections: - "api/" - REST API authentication and endpoint usage - "features/" - Runtime features: memories, sessions, knowledge, tracing - "features/memories" - Memory API endpoints for deployed agents - "security/" - RBAC, authentication, authorization - "middleware/" - JWT auth, custom middleware - "interfaces/" - Slack, WhatsApp, A2A protocol integrations - "client/" - AgentOS Python client for calling deployed agents

USE THIS TOOL for questions about:

  • Deployed agent REST API endpoints

  • Memory/session/knowledge endpoints in production

  • Authentication and security for hosted agents

  • Runtime features and middleware

For SDK code usage (writing agents), use agno_docs or agno_reference instead.

Inputs: path. Returns: result

agno_apiA

Get AgentOS REST API endpoints from the OpenAPI specification.

Args: resource: API resource to look up. One of: memory, agents, teams, workflows, sessions, knowledge, evals, traces, metrics, database, playground Leave empty to list all available API resources.

Returns detailed REST API endpoint documentation including:

  • HTTP method and path (e.g., GET /memories, POST /memories)

  • Request parameters and their types

  • Request body schema

  • Response codes and descriptions

USE THIS TOOL when the user asks about:

  • REST API endpoints for deployed AgentOS

  • HTTP methods for interacting with AgentOS

  • API schemas and parameters

  • How to call AgentOS programmatically via HTTP

For SDK/Python code (classes, methods), use agno_reference instead. For conceptual docs about features, use agno_agentos instead.

Inputs: resource. Returns: result

agno_docsA

Get Agno SDK conceptual documentation and guides for writing agent code.

Args: path: Documentation path. Use "basics/" to see all topics.

SDK Documentation Paths: - "basics/agents/" - How to create and configure agents in code - "basics/tools/" - How to create custom tools for agents - "basics/memory/" - How to use memory in your agent code - "basics/knowledge/" - Knowledge bases and RAG implementation - "basics/teams/" - Multi-agent team coordination - "basics/workflows/" - Workflow orchestration patterns

This is for SDK/library usage (writing Python code with Agno). For deployed agent REST APIs and runtime features, use agno_agentos instead.

Inputs: path (required). Returns: result

agno_examplesA

Get SDK code examples for building agents with Agno.

Args: category: Example category. One of: agents, teams, workflows, tools, memory, knowledge, models, database, evals, guardrails, hitl, multimodal, reasoning, sessions, tracing Leave empty to list all available categories.

Returns complete, runnable Python code examples with imports and setup. These are SDK examples for writing agent code, not deployment examples.

For deployment and hosting examples, use agno_agentos instead.

Inputs: category. Returns: result

agno_integrationsA

Get integration documentation for databases, vector stores, and models.

Args: integration_type: Type of integration. One of: database, vectordb, models, toolkits name: Specific integration name. Leave empty to list all of that type. Database: postgres, mongodb, sqlite, mysql, redis, dynamodb, firestore VectorDB: pinecone, qdrant, chroma, weaviate, milvus, lancedb Models: openai, anthropic, google, azure, bedrock

Examples: - integration_type="database", name="postgres" - integration_type="vectordb", name="pinecone" - integration_type="models" (lists all providers)

Inputs: integration_type (required), name. Returns: result

agno_migrationA

Get migration guides and FAQ documentation.

Args: topic: Topic to fetch. Leave empty to list all available topics. Migration guides: v2-migration, workflows-migration, installation, changelog FAQ topics: environment, openai-key, structured-outputs, docker-connection, agentos-connection, rbac-auth, switching-models, tpm, tableplus

Use for upgrading Agno versions, installation issues, and common errors.

Inputs: topic. Returns: result

agno_referenceA

Get Agno SDK class and method reference (parameters, signatures, options).

Args: topic: Reference topic. One of: agents, teams, workflows, tools, models, memory, knowledge, storage, hooks, compression, reasoning, agent-os

This provides SDK CLASS documentation (e.g., Agent() constructor parameters, MemoryManager methods, Tool decorator options).

For runtime REST API endpoints (deployed agent APIs), use agno_agentos instead.

Inputs: topic (required). Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct documentation domain (runtime APIs, SDK concepts, code examples, integrations, migration, class reference, and API endpoints). Descriptions include explicit guidance on when to use which tool, minimizing confusion.

    Naming Consistency5/5

    All tool names follow the 'agno_' prefix plus a clear, descriptive topic in snake_case (e.g., agno_docs, agno_api, agno_reference). The pattern is uniform and predictable.

    Tool Count5/5

    With 7 tools, the server covers the full scope of documentation needs for the Agno ecosystem without being overwhelming or sparse. Each tool serves a well-defined purpose.

    Completeness4/5

    The server covers most major documentation areas: SDK concepts, examples, reference, API endpoints, integrations, migration, and runtime. Minor gaps like advanced troubleshooting beyond migration could exist, but the coverage is comprehensive for typical use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with real-time access to the AGNO framework documentation by enabling them to browse, search, and fetch documentation pages. This server allows users to query information about AGNO's Agents, Teams, and Workflows directly through MCP-compatible clients.
      16
      -
    • A
      license
      A
      quality
      D
      maintenance
      Provides tools for AI agents to search, browse, and retrieve the full documentation for the mcp-framework. It enables agents to access documentation sections and page content directly within MCP-compatible environments like Claude Code and Cursor.
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides MCP tools to list and search OpenAI Agents SDK documentation, enabling LLMs to retrieve documentation topics and content via natural language queries.
      78 PyPI
      MIT