Agno 3.0.2 publishes agents, teams and toolkits as individually named MCP tools instead of one run_agent dispatcher

GitHub·high signalXBlueskyLinkedInCopy link

MCPConfig.tools now accepts Agent, Team, and Workflow instances plus Toolkit objects, exposing each as its own named MCP tool — `chief` rather than `run_agent(agent_id="chief")` — with component.as_tool(name=..., description=...) for custom naming. Toolkits publish one MCP tool per registered method, narrowed by the toolkit's own enable_*/include_tools/exclude_tools, and ToolResult values render as MCP content blocks including resource_link for URL-only artifacts. The release also adds MCP title and behaviour annotations, defaulting exposed components to readOnlyHint False, destructiveHint True, openWorldHint True.