Docker MCP Toolkit
Docker’s MCP Toolkit gives the clients you connect to Docker, such as Claude Desktop, VS Code or Cursor, the tools of every server in your profile. Adding Actera there lets them work with one Actera workspace: ask what your agents did, draft a policy from a real decision, or find out what is waiting for approval.
The server is for the people running Actera. It does not enforce anything: agents are still governed through the Claude Code plugin, the Codex plugin, the GitHub Copilot plugin or an SDK.
Before you start
Section titled “Before you start”You need an Actera account and Docker Desktop with the MCP Toolkit turned on. Reading works for every workspace member. Changing policies and agents needs the owner or admin role.
Connect in Docker Desktop
Section titled “Connect in Docker Desktop”- Open MCP Toolkit and select the Catalog tab.
- Find Actera and add it to your profile.
- Open the server’s Configuration tab, select OAuth and follow the link.
- Your browser opens Actera. Sign in if needed, choose one workspace and confirm. Actera then offers the same agent setup as the Overview. Select Back to Docker within 5 minutes to finish, because Docker stops waiting after that. You can set up an agent from the Overview afterwards.
- In the Clients tab, connect the client you want to use, then restart it if it was running.
Each connection covers one workspace. To work with another workspace, disconnect and connect again, choosing the other one.
Connect from the command line
Section titled “Connect from the command line”With Actera in a profile, authorize it and run the gateway:
docker mcp oauth authorize acteradocker mcp gateway run --profile <profile>docker mcp oauth authorize prints a link to open if the browser does not start. The server’s address is:
https://mcp.actera.dev/mcpTry it
Section titled “Try it”- “Which agents did the most this week, and what was blocked?”
- “What is waiting for approval, and why?”
- “Explain why this decision was blocked, then draft a policy that would allow it for refunds under £50.”
- “Would this agent be allowed to delete a production database under our current policies?”
What it can do
Section titled “What it can do”Every client connected to your Docker profile acts as you, with your role in the workspace.
| Area | Without changing anything | Owner or admin only |
|---|---|---|
| Workspace | See the workspace, your role and the plan | |
| Agents | List agents and read their configuration | Register an agent, or set its name, policies and what happens when no policy matches |
| Decisions | Search, read and summarize decisions, and list pending approvals | |
| Policies | Search and read policies, see fields observed in real traffic, simulate an action and start a draft from a decision | Check, save, discard and publish drafts |
Every tool that changes data is marked as destructive, so clients that ask before such tools ask you first. Publishing a policy applies it at once to every agent it is assigned to, and it runs the draft’s tests first. Publishing stops if any test fails.
What it cannot do
Section titled “What it cannot do”It cannot approve or reject decisions. It gives you a link, and an eligible person decides in Actera. It also cannot see members, API keys or other workspaces.
Understand what is shared
Section titled “Understand what is shared”Actera sends the results of the tools a client calls through Docker’s gateway to that client. Those results can include decision details, the tool names and inputs your agents sent, policies, and agent configuration. See the privacy policy for how Actera handles data.
Decision inputs come from your agents, so they can contain text written by other people or systems. Clients are told to treat them as data, not instructions. Review anything important in Actera before acting on it.
Changes made through Docker are recorded in the workspace audit trail with the connection that made them.
Disconnect
Section titled “Disconnect”In Actera, open the workspace’s Settings and find Connected apps, where the connection is listed as Docker. Disconnect stops it immediately. You only see your own connections.
Revoking Actera in Docker’s OAuth tab, or with docker mcp oauth revoke actera, removes the token from Docker. Use Disconnect in Actera to make sure access stops.
Troubleshooting
Section titled “Troubleshooting”“This link no longer works.” Sign-in links last 10 minutes and work once. Authorize Actera in Docker again.
“Workspace administrator access is required.” The change needs an owner or admin. Ask one to make it, or to change your role.
Actera’s tools stop working. The connection was disconnected, or its sign-in expired after 30 days without use. If a sign-in credential is ever used twice, Actera also ends the connection as a precaution. Authorize Actera in Docker again.
Company sign-in. If your workspace uses company sign-in, Actera asks you to complete it before connecting, and the tools stop working if your access there ends.