MCP Demo
Expose AgentOS agents and custom tools through MCP with OAuth, dynamic headers, and managed MCPTools lifespans.
Serve AgentOS to MCP clients, or consume another server’s tools from an agent. The default server exposes eight built-in tools; custom configurations can select a different surface.
| Example | Description |
|---|---|
| Dynamic Headers | Send request-specific values to an MCP server through HTTP headers. |
| MCP Tools | Connect MCPTools to the filesystem MCP server over a stdio session and summarize a file. |
| Serve AgentOS over MCP | Expose one agent through the eight built-in AgentOS MCP tools at /mcp. |
| Expose one custom MCP tool | Replace the eight built-in AgentOS MCP tools with one purpose-built tool. |
| Drive the AgentOS MCP run lifecycle | Use a protocol-level FastMCP client to discover the eight built-in tools, pause and continue one agent run, cancel a second paused run, and read the continued session back. |
| Use WorkOS AuthKit for MCP OAuth | Keep AgentOS as the MCP resource server while WorkOS AuthKit owns login, consent, and token issuance. |
| Use the built-in MCP authorization server | Make AgentOS its own OAuth 2.1 authorization server for MCP connector clients. |
| Secure and scope an AgentOS MCP server | Protect /mcp with an OS security key plus a database-backed agno_pat_ service account. |
| Agents as named tools | Publish selected components as named MCP tools. |
| Toolkit tools | Expose toolkit functions through the native MCP server. |
| Server identity | Set the server name, version, and initialize instructions. |
| Stateless transport | Handle requests without retained MCP transport sessions. |
| Public documentation tools | Serve explicit page search, read, and grep tools alongside public chat. |