Bring any tool in through MCP, and take AgOS with you.

MCP servers as tools for your agents

Add an MCP server and its tools are available to AgOS agents. Adding one is a setting, not a code change. Tool calls that act on the outside world can wait in Approvals.

• Cloud: remote MCP servers.
• Isolated Cloud: remote and local MCP servers.

MCP tools start on the Team plan; see pricing.

AgOS as an MCP server

Claude, ChatGPT, Codex and other MCP clients can connect to AgOS. Once connected, a client can:

• Save a Markdown document as a page in Knowledge, or append to an existing page.
• Search Knowledge and open a page.
• List spaces and create new ones.

Pages a client saves go into a space named after it, such as "Claude Code", and carry the signed-in person as their author. Saving again with the same key updates the page instead of making a copy.

Sign-in with consent

Clients connect over OAuth 2.1, so there is no API key to copy around. The client opens AgOS in your browser, you sign in, and a consent screen names the client and what it is asking for. Nothing is issued until you press Allow.

Lessons that a person approves

An agent working through MCP can propose a reusable lesson, such as how this team runs its migrations. It stays inert until a person approves it. Only then is it shared with later agent work, because approving it is the moment it starts steering other agents.