Tools

Integrate external tools into your agents via Model Context Protocol (MCP) servers or web search.

provider: agno
resource: tools/mcp
name: my-tools
config:
  url: "https://mcp.example.com/sse"
  headers:
    Authorization: "Bearer your-token"
  include_run_context_headers: true
  timeout_seconds: 30

provider: agno
resource: tools/mcp
name: local-tools
config:
  command: "npx -y @modelcontextprotocol/server-filesystem /data"
  env:
    LOG_LEVEL: "info"

provider: agno
resource: tools/websearch
name: search
config:
  enable_search: true
  enable_news: true
  backend: duckduckgo

​

Dependencies

• agno/agent — in the tools list
• agno/team — in the tools list

​

Notes

• For MCP tools, you must provide exactly one of command or url.
• The transport type is auto-detected if not specified: command implies stdio, url implies sse.
• env and headers take either a map of literal strings or a single field reference whose resolved value is the whole map. A field reference on an individual value is rejected when you apply the resource.
• env and headers are not sensitive fields: their values are shown as written.
• The include_run_context_headers option forwards the agent’s user ID, session ID, and run ID as HTTP headers to the MCP server.
• Web search requires the ddgs package, which is automatically included as a pip dependency.