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

> AgentOS now serves each agent, team, workflow, and toolkit you pass to MCPConfig.tools as its own named MCP tool, so a client calls it by name instead of through a generic run tool.

- Published: 2026-08-30
- Author: Ashpreet Bedi
- Categories: Changelog
- Canonical: https://www.agno.com/articles/agentos-now-publishes-agents-teams-workflows-and-toolkits-as-named-mcp-tools
- Markdown: https://www.agno.com/articles/agentos-now-publishes-agents-teams-workflows-and-toolkits-as-named-mcp-tools.md

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")`.

```python
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](https://docs.agno.com/features/mcp-server) in the docs.