← All guides

What an agent can do through the MCP server

Once connected, an outside agent can create and manage workspaces and their conversations, write and edit Domains, register repositories, define and assign canned Agents, configure Connectors, build and instantiate Strategies, save Macros, and read or write Memories — essentially the entire surface of the app itself.

Relationships — attaching a Domain or repository to a workspace, or assigning an Agent to one — aren't separate actions to learn; they're just part of updating the workspace itself, mirroring exactly how the app treats them internally.

A handful of things are deliberately left off this surface — mostly local-filesystem discovery helpers built for the app's own UI (verifying a path is a real repo, guessing dev-server presets) rather than anything an agent registering a repo it already knows the path to would need.