
Agent Sudo Mcp
Add authorization, delegation, provenance, and audit controls around agent actions exposed through MCP.
Overview
agent-sudo-mcp is an MCP server for the Ship phase that adapts Agent_Sudo authorization, delegation, provenance, and audit for agent tool hosts.
What is this MCP server?
- MCP adapter for Agent_Sudo governance primitives
- Authorization and delegation boundaries for tool-using agents
- Provenance tracking for agent-originated actions
- Audit-oriented surface for reviewing agent behavior
- PyPI stdio package agent-sudo-mcp (0.5.5)
- Server version 0.5.5
- PyPI package identifier agent-sudo-mcp
- stdio MCP transport
What problem does it solve?
Autonomous agents can invoke powerful MCP tools with no standardized way to authorize actions, delegate scope, or prove what happened afterward.
Who is it for?
Solo builders running multi-tool agents in production who need governance without building a custom auth audit plane.
Skip if: Hobby prompts with no tool side effects or teams with zero appetite for policy design around agents.
What do I get? / Deliverables
After registration, your agent stack can route sensitive operations through Agent_Sudo policies and retain audit-friendly provenance via MCP.
- Policy-gated agent tool execution path
- Delegation and provenance metadata for agent runs
- Audit-oriented MCP surface aligned with Agent_Sudo
Recommended MCP Servers
Journey fit
How it compares
Governance MCP adapter for Agent_Sudo, not a feature-integration skill or generic logging plugin.
Common Questions / FAQ
Who is agent-sudo-mcp for?
Builders shipping agentic workflows who need MCP-accessible authorization, delegation, and audit via Agent_Sudo.
When should I use agent-sudo-mcp?
Use it when agents can mutate data, spend money, or access secrets and you need enforced scope plus provenance before launch or in operations.
How do I add agent-sudo-mcp to my agent?
Register the PyPI agent-sudo-mcp stdio server in your MCP config and connect it to your Agent_Sudo deployment per the upstream Agent_Sudo documentation.