AgentOS now publishes agents, teams, workflows, and toolkits as named MCP tools

We added first-class MCP publishing for your components. MCPConfig.tools now accepts Agent, Team, Workflow, and Toolkit instances, and AgentOS serves each one as its own named tool. An MCP client calls chief directly instead of calling run_agent(agent_id="chief").

from agno.os import AgentOS, MCPConfig
 
agent_os = AgentOS(
    agents=[chief],
    mcp=MCPConfig(tools=[chief]),  # published as an MCP tool named "chief"
)

Before this, clients ran your components through a generic tool like run_agent and passed the id as an argument. Now each component is a first-class tool with its own name and description. We keep framework parameters out of the client schema so the model only sees what it needs, and a ToolResult return renders as MCP content blocks. Each tool also carries a title and behavior annotations.

Learn more about the AgentOS MCP server in the docs.