Claude connector
The Actera connector lets you work with one workspace from Claude. Ask what your agents did, draft a policy from a real decision, or find out what is waiting for approval.
The connector is for the people running Actera. It does not enforce anything: agents are still governed through the Claude Code plugin, the Codex plugin or an SDK.
Before you start
Section titled “Before you start”You need an Actera account. Reading works for every workspace member. Changing policies and agents needs the owner or admin role.
Connect
Section titled “Connect”In claude.ai, open Customize → Connectors → Add → Add custom connector. Name it Actera and enter this URL:
https://mcp.actera.dev/mcpSelect Connect. Claude sends you to Actera, where you sign in if needed, choose one workspace and confirm. Claude Desktop, mobile and Cowork use the same connection.
In Claude Code, add it from a terminal and complete the same browser step:
claude mcp add --transport http --scope user actera https://mcp.actera.dev/mcpclaude mcp login acteraEach connection covers one workspace. To work with another workspace, disconnect and connect again, choosing the other one.
Try 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 Claude can do
Section titled “What Claude can do”Claude 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 |
Reading policies and agents is open to every member. Checking a draft is read-only but needs an owner or admin.
Claude asks before any tool that changes data, unless you have changed that tool’s permission in the connector’s settings. 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 Claude cannot do
Section titled “What Claude cannot do”Claude cannot approve or reject decisions. It gives you a link, and an eligible person decides in Actera. Claude also cannot see members, API keys or other workspaces.
Understand what is shared
Section titled “Understand what is shared”When you use the connector, Actera sends Claude the results of the tools it calls. 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. Claude is told to treat them as data, not instructions. Review anything important in Actera before acting on it.
Changes made through Claude 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 Claude. It lists your connections and when each was last used. Disconnect stops that connection immediately. You only see your own connections.
Removing the connector in Claude does not end the connection in Actera, so use Disconnect when you want access to stop.
Troubleshooting
Section titled “Troubleshooting”“This link no longer works.” Sign-in links last 10 minutes and work once. Go back to Claude and select Connect again.
“Workspace administrator access is required.” The change needs an owner or admin. Ask one to make it, or to change your role.
Claude asks you to connect again. 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. Connect again to continue.
“The result is too large to return.” Ask for a narrower time range, a single agent, or fewer items.
A search misses older decisions. Searches cover seven days by default and up to 31 days at a time. Ask for the dates you need. Pending approvals are always listed in full, however old they are.
Company sign-in. If your workspace uses company sign-in, Actera asks you to complete it before connecting, and Claude stops working if your access there ends.