managed-agent-control-mcp
managed-agent-control-mcp
Start, observe, and interact with Claude Managed Agents from any MCP client (Claude.ai, Claude Code, Cursor, mcp-remote, your own agent, …).
Claude Managed Agents run on Anthropic's platform — each is an agent definition
(model, system prompt, tools, skills) that executes inside a sandbox environment.
This MCP server puts a remote control on those agents: connect it to any MCP
client and you can launch an agent, watch what it does, reply to it, approve the
tools it wants to run, and stop it. Claude.ai is the showcase client (do it all
from a normal conversation), but the same tools work from Claude Code, Cursor,
mcp-remote, the MCP Inspector, or a custom MCP client. It is the runtime
companion to the Terraform provider
that defines agents declaratively.
It runs as a local stdio server, a generic HTTP container, or on AWS Lambda, with pluggable inbound auth (static bearer, generic OIDC, or an AWS Cognito preset).
This is a community project. It is not maintained by, endorsed by, or affiliated
with Anthropic. The Managed Agents API is a beta API (managed-agents-2026-04-01).
How it works
MCP client ──MCP──▶ managed-agent-control-mcp ──HTTPS (x-api-key)──▶ Managed Agents API
(Claude.ai, (this server: tools + auth) (agents run here)
Claude Code, …)You drive a loop: discover an agent → start a session → observe by
polling events → interact (reply / interrupt / approve tools) → end.
Because MCP tool calls are request/response, observation is by polling
(session_events / session_get) — there is no live stream into the chat.
Related MCP server: claude-octopus
Quickstart (local, <2 min)
You need an ANTHROPIC_API_KEY with Managed Agents access and
uv.
git clone https://github.com/modus-agendi/managed-agent-control-mcp
cd managed-agent-control-mcp
uv sync
# Run the server over stdio:
ANTHROPIC_API_KEY=sk-ant-... uv run python -m managed_agents_mcpExplore the tools interactively with the MCP Inspector:
ANTHROPIC_API_KEY=sk-ant-... npx @modelcontextprotocol/inspector \
uv run python -m managed_agents_mcpRegister it with Claude Code (a project-scoped .mcp.json is included):
claude mcp add managed-agent-control -- uv run python -m managed_agents_mcpOnce published to PyPI, you can skip the clone: uvx managed-agent-control-mcp.
Tools
Tier | Tool | Does |
Discover |
| Find an agent and inspect its config |
| Find a sandbox environment | |
| Find a credential vault to attach at | |
| Find a persistent memory store | |
Start |
| Create a session and (optionally) send the first instruction |
Observe |
| Status ( |
| List sessions | |
| Poll the agent's output/activity (cursor + type filter) | |
Interact |
| Send a message / continue a turn |
| Stop or redirect a running agent | |
| Approve/deny a tool the agent is waiting on | |
Destructive 🔒 |
| Archive (keep history) or delete |
See docs/tools.md for every argument and return shape.
Configuration
Only ANTHROPIC_API_KEY is required for local use. Full reference in
docs/configuration.md.
Env var | Purpose |
| Required. Operator key the server acts with. |
| Override the API base URL (gateways/testing). |
| Inbound auth for HTTP: |
| Shared token for |
| JWT verification for |
|
|
| Agents |
|
|
Authentication
There are two auth layers (kept separate by design):
Outbound — how this server calls Anthropic: your
ANTHROPIC_API_KEY.Inbound — how MCP clients authenticate to this server. Pluggable and required for any HTTP deployment:
bearer — a shared static token. Simplest; works with Claude.ai connectors and
mcp-remote.oidc — verify JWTs from any OIDC provider (Auth0, Okta, Keycloak, Entra, Cognito).
cognito — the OIDC verifier plus the hosted-UI OAuth facade Cognito needs.
Setup and Claude.ai connector onboarding: docs/authentication.md.
Never expose an HTTP deployment without an inbound auth mode set. Anyone who passes inbound auth can drive your Anthropic key — scope the key and use theguardrails.
Deployment
Target | How |
Local (stdio) |
|
Container (HTTP) |
|
AWS Lambda | Self-contained Terraform module in |
Details: docs/deployment.md.
Documentation
Configuration — every env var + guardrails
Authentication — bearer / OIDC / Cognito + Claude.ai setup
Deployment — local, container, Lambda
Architecture — module map, the two auth layers, the polling model
Tools — full tool reference
Examples — end-to-end deployment walkthroughs (host + OAuth provider)
Contributing
Contributions welcome — see CONTRIBUTING.md and the Code of Conduct. Found a security issue? See SECURITY.md.
License
MIT — see LICENSE. Maintained by Andrei Svirida.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseAqualityDmaintenanceA TypeScript MCP server for launching, tracking, and managing external coding-agent runs across local and remote backends like Codex and Claude Code. It allows top-level agents to orchestrate subagents through tools for spawning tasks, polling events, and handling interactive sessions.Last updated72
- AlicenseAqualityDmaintenanceWraps the Claude Agent SDK as MCP servers, letting you spawn multiple specialized Claude Code agents — each with its own model, tools, system prompt, and personality — from any MCP client.Last updated511216ISC
- Flicense-qualityDmaintenanceA Model Context Protocol (MCP) server for Dust.tt agents, designed for seamless integration with Claude Desktop via STDIO. Provides robust agent querying, listing, and configuration tools.Last updated7
- Alicense-qualityDmaintenanceAn MCP server that wraps the Claude Agent SDK, enabling Claude-powered queries, coding tasks, web search, and customizable agent execution using OAuth without an API key.Last updated15MIT
Related MCP Connectors
Real-time chat hub for AI agents — Claude Code, Cursor, Cline, Codex over MCP or REST.
Hosted AgentLux MCP server for marketplace, identity, creator, services, and social flows.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/modus-agendi/managed-agent-control-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server