About DockaShell
DockaShell is an MCP server that gives AI agents isolated, persistent Docker containers with shell access and file operations. Every command and file change is logged for audit. The project is research software and not production-ready.
Key features
- 01Isolated persistent container per agent
- 02Shell access and file operations
- 03Audit log of commands and file changes
- 04Global npm install with command line management
Use cases
- 01Agent processing CSV files in an isolated Python environment
- 02Agent building and running a web development project
- 03Agent keeping a SQLite database across sessions
MCP support
The project is an MCP server that exposes shell and file operation tools to MCP clients. It records agent actions in an audit trail.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEDockaShell
DockaShell is an MCP (Model Context Protocol) server that gives AI agents isolated Docker containers to work in. Each agent gets its own persistent environment with shell access, file operations, and full audit trails.
This is a research project exploring agent autonomy: How far can we push shell-based workflows? Can agents manage their own development environments and create their own tools?
Why this exists
Current AI assistants hit fundamental walls:
- No persistent memory: Conversations reset, context is lost, agents can't build on previous work
- Tool babysitting: Every shell command needs human approval, breaking agent flow and autonomy
- Limited toolsets: Agents stuck with predefined tools instead of building what they need
- No self-reflection: Can't analyze their own traces to improve or learn from past sessions
DockaShell removes these constraints to explore what emerges:
- Self-evolving agents: Build and refine their own tools, scripts, and workflows
- Continuous memory: Maintain knowledge bases, wikis, notebooks that persist across sessions
- Autonomous exploration: Run shell commands without constant human intervention
- Meta-learning: Analyze previous traces to improve decision-making and tool usage
The core question: What can agents accomplish when they have real persistence and autonomy?
How it works
AI Agent (Claude/GPT/...)
↔ DockaShell (MCP Server)
└─ Docker Engine
├─ Container A (Project 1)
│ └─ Persistent Volume
├─ Container B (Project 2)
│ └─ Persistent Volume
└─ Container C (Project 3)
└─ Persistent Volume
Each AI agent gets its own isolated Docker container with persistent storage. Instead of dozens of custom tools, agents use standard shell commands (bash, git, npm, etc.) and build their own workflows.
Key principles:
- Shell > specialized tools: Agents already "speak" POSIX, so let them use real commands
- Container isolation: Full autonomy inside, zero risk to your host system
- Persistent workspace: Files, databases, and context survive across sessions
- Complete audit trail: Every command and file change is logged for analysis
→ See detailed architecture and security model
Quick Start
# Install
npm install -g dockashell
# Setup
dockashell build
dockashell create my-project
dockashell start my-project
Add to your MCP client configuration:
{
"mcpServers": {
"dockashell": {
"command": "dockashell",
"args": ["serve"]
}
}
}
Requirements: Node.js 20+, Docker running
Example workflows
Data analysis: Agent spins up Python environment, processes CSV files, generates insights
Web development: Agent builds React app, installs dependencies, runs dev server with live preview
Research assistant: Agent tracks information across sessions, maintains SQLite databases, remembers context
Documentation
- CLI usage - Commands and workflow examples
- Configuration - Global and project settings
- MCP tools - Complete tool reference for agents
Current state
This is active research, not production software. The core functionality works well for experimentation, but expect changes as I explore what agents can do with persistent shell environments.
Contributions and feedback welcome.
License
Apache License 2.0
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.