# Extend the AgentOS MCP server with custom, scoped, identity-aware tools

> The AgentOS MCP server at /mcp is now a real extension point, configured through a single MCPServerConfig object rather than custom middleware.

- Published: 2026-06-15
- Author: Agno Team
- Category: Changelog
- Canonical: https://agno-com-nine.vercel.app/articles/extend-the-agentos-mcp-server-with-custom-scoped-identity-aware-tools
- Markdown: https://agno-com-nine.vercel.app/articles/extend-the-agentos-mcp-server-with-custom-scoped-identity-aware-tools.md

The AgentOS MCP server at `/mcp` is now a real extension point, configured through a single `MCPServerConfig` object rather than custom middleware. You can register your own tools as plain callables or Agno `@tool`/`Function` objects, and scope the built-ins by turning them off with `enable_builtin_tools=False` or filtering with `include_tags`/`exclude_tags`. A tool can receive the authenticated caller's identity by declaring `user_id`, which AgentOS fills from the JWT subject while hiding it from the client-facing schema, so a tool acts on behalf of the real caller without exposing that field. You can gate calls with a one-line `authorize` function and switch on built-in DNS-rebinding protection through `allowed_hosts`/`allowed_origins`, all expressed as data. It stays fully backward compatible: with no `mcp_config`, the built-in tools register exactly as before.

See the [AgentOS MCP docs](https://docs.agno.com/agent-os/usage/mcp/enable-mcp-example) for setup.