automo.aiBuild Docs
MCPWorkspaces, permissions and credits
Updated 4 Nov 20261 min readView as Markdown

Workspaces, permissions and credits

Whose access it uses, which workspace a call lands in, and what it costs.

The server acts as you. It does not get access of its own.

Permissions

Your AI tool has your identity, all your workspaces and the same roles you have. Nothing the app refuses is allowed here.

Which workspace a call uses

  1. The workspace named on the call, if there is one.
  2. Otherwise, the workspace of the project.
  3. Otherwise, the current workspace for this connection. Set it with automo_switch_workspace; automo_whoami shows it.
  4. Otherwise, the workspace you last used in the app.

Plan-gated features

Features that depend on your plan, such as proactive workflows and the workflow architect, Security and Guardrails, are never hidden. Calling one on a plan without it returns a "not available" answer naming the plan needed, what it would have done, an upgrade link and an alternative.

Credits

Agent turns started from MCP bill exactly as they do from the app, to the workspace the session runs in. The server's own calls are free.

Rate limits stop runaway loops. See How credits work.

Was this page helpful?

Previous: Long-running work, reviews and publishingNext stepTroubleshooting