DockaShell MCP Server

DockaShell is an MCP server that gives AI agents isolated Docker containers to work in. MCP tools for shell access, file operations, and full audit

Local serverstdioPython

What is the DockaShell MCP server?

Most knowledge and memory work still happens through a UI a human drives. DockaShell MCP server moves it into the conversation instead. DockaShell is an MCP server that gives AI agents isolated Docker containers to work in. MCP tools for shell access, file operations, and full audit trail.

The short version

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.

  • 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
  • Self-evolving agents — Build and refine their own tools, scripts, and workflows
  • Continuous memory — Maintain knowledge bases, wikis, notebooks that persist across sessions

Getting it running

dockashell on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

The tools it exposes

The server publishes 2 tools. What each one is for:

  • Self — evolving agents**: Build and refine their own tools, scripts, and workflows
  • Meta-learning — Analyze previous traces to improve decision-making and tool usage

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. DockaShell's toolset — Self, Meta-learning — is a fair guide to whether it matches your workflow. It is maintained by anzax; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
Selfevolving agents**: Build and refine their own tools, scripts, and workflows
Meta-learningAnalyze previous traces to improve decision-making and tool usage

How to install the DockaShell MCP server

Add to your MCP client configuration:

```json
{
  "mcpServers": {
    "dockashell": {
      "command": "dockashell",
      "args": ["serve"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use DockaShell to Self.
  • Use DockaShell to Meta-learning.

Frequently asked questions

It addresses no persistent memory, tool babysitting, limited toolsets, and lack of self-reflection in current AI assistants.