Loading features...
Loading features...
Features · Tools & Connectors
The workspace is designed around tools that do real work: MCP servers, OAuth connectors, and web search. One rule everywhere. A tool runs only with a permission you set, and the route stays visible before anything leaves your device.
The tool surface
Permission model
| Discovery | Connecting a server lists its tools. Nothing runs at discovery. Tools wait for a permission you set. |
| Permission | Each tool carries its own setting: Always allow, Needs approval, or Blocked. |
| Approval | When a tool needs approval, you review the request before it runs, in the Desktop app or the CLI overlay. |
| Boundary | Local, BYOK, and AGI Cloud stay separate. Tool calls never silently cross from one mode to another. |
In the terminal
The agi CLI runs tools inside a sandbox with explicit approvals, connects MCP servers over stdio, SSE, or Streamable HTTP with optional OAuth, and can expose itself to any MCP client with agi mcp-server.
Public launch: July 12, 2026
Browse the connector directory, wire up your own MCP servers, and keep every tool call behind a permission you set.
Public launch · July 12, 2026