dockashell
Provides isolated Docker containers for AI agents, enabling persistent shell access, file operations, and automation of development environments with full audit trails.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@dockashellcreate a new React app and install dependencies"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
DockaShell
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?
Related MCP server: PiloTY
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 VolumeEach 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-projectAdd 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
This server cannot be installed
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
- Alicense-qualityCmaintenanceRuns isolated AI agents in Docker containers with persistent workspaces and conversation history. Each agent has access to file operations, shell commands, GitHub integration, and can connect to external MCP servers for additional tools.Last updated3MIT
- AlicenseBqualityFmaintenancePiloTY is an MCP server that provides AI agents with a persistent, interactive terminal, enabling long-running commands, log monitoring, and stateful shell interactions across tool calls.Last updated1743Apache 2.0
- AlicenseAqualityDmaintenanceA production-ready MCP server that enables AI assistants to execute shell commands, manage files, monitor system resources, and automate complex workflows with advanced features like stock tracking and web automation.Last updated743MIT
- Alicense-qualityDmaintenanceA production-ready MCP server that equips AI agents with dynamic, persistent, and executable skills. It enables secure script execution and progressive disclosure to reduce context window usage.Last updated6MIT
Related MCP Connectors
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.
Cloud-hosted MCP server for durable AI memory
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/anzax/dockashell'
If you have feedback or need assistance with the MCP directory API, please join our Discord server