# Druks

> Autonomous software delivery on your own Claude/Codex subscriptions — durable runs, human gates, sandboxed agents. Build ships out of the box; Druks is the self-hosted home for durable agent apps.

- **Type:** MCP server
- **Install:** `agentstack add mcp-czpython-druks`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [czpython](https://agentstack.voostack.com/s/czpython)
- **Installs:** 0
- **Category:** [Databases](https://agentstack.voostack.com/c/databases)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [czpython](https://github.com/czpython)
- **Source:** https://github.com/czpython/druks
- **Website:** https://druks.ai

## Install

```sh
agentstack add mcp-czpython-druks
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Druks

> [!WARNING]
> Druks is under active development. Expect breaking changes and rough edges
> before 1.0; `main` and `latest` are edge builds, not stable releases.

Druks is the self-hosted **home for durable agent apps**, running on the
Claude and Codex subscriptions you already pay for. Ship comes bundled:
autonomous software delivery from ticket to reviewed pull request.

An ordinary agent script loses its place when the process dies. A Druks
workflow records the result of each completed durable operation in Postgres.
After a restart or deploy, Druks replays the workflow and reuses those recorded
results instead of repeating completed work. If the process was interrupted
*inside* an operation, that operation may run again, so side effects still need
idempotency. [Durability and recovery](docs/concepts.md#durability-and-recovery)
explains the exact boundary.

## Install

The installer supports three sandbox profiles backed by
[Drukbox](https://github.com/czpython/drukbox):

- `exe` (default) and `aws`: remote sandbox VMs, with Druks and Drukbox in Compose
- `docker`: local sandbox containers, with Drukbox running on the host

For a remote install:

```bash
bash  extension workflow ──> durable step ──> agent ──> sandbox
                 │                     │              │
                 │                     │              └─ Claude or Codex harness
                 │                     └─ result checkpointed in Postgres
                 ├─ event ──> feed / extension reaction
                 └─ gate  ──> wait for human or external system ──> resume
```

**Platform and applications stay separate**

Druks owns the execution and operating substrate:

- DBOS workflows and queues backed by Postgres
- typed human gates, cancellation, schedules, and observable run state
- Claude and Codex harness dispatch through isolated Drukbox sandboxes
- append-only events, live feeds, webhooks, notifications, MCP servers, and skills
- validated operator settings, encrypted MCP/OAuth secrets, and the dashboard shell
- extension discovery, API namespaces, and independent migration histories

An **extension** owns the application: its workflows, agents, domain models,
routes, events, provider reactions, and optional dashboard pages. It is a normal
Python distribution registered through the `druks.extensions` entry-point
group. Installing the distribution registers it; Druks does not need an
extension-specific plugin list.

The bundled `ship` extension is a concrete example. It coordinates coding
agents through tickets and GitHub pull requests, but GitHub PR orchestration is
`ship` behavior—not the definition of Druks.

## Documentation

- **Evaluating Druks:** [Concepts and guarantees](docs/concepts.md)
- **Installing locally:** [Full local setup](docs/full-local.md)
- **Operating a remote stack:** [Deployment runbook](deploy/README.md)
- **Configuring integrations and secrets:** [Configuration](docs/configuration.md)
- **Building an application:** [Writing an extension](docs/writing-an-extension.md)
- **Diagnosing a run or service:** [Troubleshooting](docs/troubleshooting.md)
- **Contributing to Druks:** [Contribution guide](CONTRIBUTING.md)
- **Reporting a vulnerability:** [Security policy](SECURITY.md)
- **All documentation:** [Documentation index](docs/index.md)

## Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [czpython](https://github.com/czpython)
- **Source:** [czpython/druks](https://github.com/czpython/druks)
- **License:** MIT
- **Homepage:** https://druks.ai

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** yes
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** yes
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/mcp-czpython-druks
- Seller: https://agentstack.voostack.com/s/czpython
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.