Agent Godmode
Give your agent sandboxed file access and argv-only shell commands inside a fixed workspace root while you bring your own prompts and model.
Overview
Agent Godmode is an MCP server for the Build phase that provides a sandboxed workspace with file ops, directory listing, and argv-only command execution.
What is this MCP server?
- Sandboxed workspace root via AGENT_GODMODE_ROOT or CLI --root
- File operations and list_files scoped under that directory only
- run_command restricted to argv-only invocation (no shell injection path)
- BYO LLM prompts—you control the model and orchestration layer
- PyPI package agent-godmode v0.1.9 with stdio MCP transport
- Version 0.1.9 on PyPI identifier agent-godmode
- Documented env var AGENT_GODMODE_ROOT for workspace root
- Repository: github.com/mdvohra/agent-godmode
What problem does it solve?
Letting agents run shell and file tools on your laptop feels risky without a hard root boundary and argv-only commands.
Who is it for?
Solo builders who want a minimal, root-scoped MCP workspace for agent-driven coding on a single repository.
Skip if: Builders who need multi-machine deploy orchestration, container fleets, or unconstrained system administration from the agent.
What do I get? / Deliverables
After configuring Agent Godmode, your agent can work inside one project tree with MCP-guarded file and command tools instead of a full open shell.
- Root-bound MCP tools for files, listings, and argv-only commands
- Reduced blast radius compared to unconstrained local shell tools
- Repeatable agent workspace boundary for one solo project
Recommended MCP Servers
Journey fit
Sandboxed workspace tooling is how solo builders safely let agents touch the repo during Build, before you harden Operate policies. Agent-tooling subphase because it is the MCP surface for file ops, listing, and controlled run_command—not frontend UI or payment integrations.
How it compares
Sandboxed workspace MCP, not a hosted cloud dev environment or a turnkey autonomous coding agent.
Common Questions / FAQ
Who is Agent Godmode for?
Indie developers wiring MCP agents who need filesystem and command access limited to one workspace directory.
When should I use Agent Godmode?
Use it during Build when your agent must edit files, list paths, or run argv-only CLI tools inside a repo you explicitly root-bind.
How do I add Agent Godmode to my agent?
Install Agent Godmode from PyPI (v0.1.9), set AGENT_GODMODE_ROOT to your project path or use --root, and register the stdio server in your MCP client config.