Let agents use configured integrations

Built-in MCP tools and skills help sessions discover resources and request access. Review exact configuration commands where you approve them: Approve opens a request’s unreviewed commands in place, and a or d then decides exactly that request. Approved plans run in order on the server, even with your console closed; rules delivery and host-job completion stay separate. Operator tools configure local folders and network templates, and call controller operations through typed tools.

How it works

  1. MCP Approvals

    Inspect the requested actions and approve scoped access.

  2. Inspect permission details

    Enter reveals requested actions, limits and purpose before a decision.

  3. Back to repository requests

    Esc returns to the repository summary without making a decision.

  4. Approve and deliver sequentially

    Approve the repository requests; rules reach the retained session one at a time.

  5. Verified permission history

    History shows that all three approvals reached the session.

  6. Review current container limits

    A typed request names the exact running container, affected sessions and configured budget. The requested RAM and CPU totals are separate from current limits; this sample has no execution-host proof.

Read the documentation

Try the interface

INTERACTIVE DEMO

Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.

Watch the workflow

MCP ApprovalsREAL UI

Loading the recorded terminal…

Walkthrough paused
YOUR AGENTS. YOUR INFRASTRUCTURE.

Put your server to work.

Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.