OpenCode Workbench: a reproducible, self-documenting, recoverable OpenCode development workstation — configuration, agent skills, MCP stack, and a clone MCP server for any Linux box
- ✓Open-source license (MIT)
- ✓Actively maintained (<30d)
- ✓Clear description
- ✓Topics declared
- ✓Documented (README)
claude mcp add opencode-workbench -- npx -y playwright{
"mcpServers": {
"opencode-workbench": {
"command": "npx",
"args": ["-y", "playwright"]
}
}
}Resumen de MCP Servers
# OpenCode Workbench
<!-- mcp-name: io.github.simonmak-ascent/opencode-workbench -->
> **A reproducible, self-documenting, and recoverable OpenCode development workstation** — configuration, agent skills, MCP stack, and an MCP server that clones the entire setup onto any Linux machine (locally or over SSH).
[](https://github.com/simonmak-ascent/opencode-workbench/actions/workflows/secret-scan.yml)
[](https://github.com/simonmak-ascent/opencode-workbench/actions/workflows/tdqs.yml)
[](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.simonmak-ascent/opencode-workbench)
[](https://glama.ai/mcp/servers/simonmak-ascent/opencode-workbench)
[](https://github.com/simonmak-ascent/opencode-workbench/actions/workflows/mcp-server.yml)
[](https://github.com/simonmak-ascent/opencode-workbench/actions/workflows/validate-docs.yml)
[](LICENSE)
**Homepage & remote MCP:** https://opencode-workbench.simonmak.com · `POST https://opencode-workbench.simonmak.com/mcp`
## Overview
This repository is the **single source of truth** for a complete cloud development workstation. Everything needed to rebuild from scratch is versioned here:
- Workstation configuration and automation
- OpenCode configuration (model, providers, MCP servers)
- Agent skills (45 reusable AI instructions across research, dev, data, science and ops)
- Operational prompts (disaster recovery, backup, security)
- Recovery procedures (playbook, checklist, gap analysis)
- Security governance (secret management, threat model)
- OpenCode sandbox (bubblewrap) — run the agent with a read-only system and no secret mounts
- **`opencode-workbench`** — an MCP server that installs this profile on any Linux box
**No important knowledge exists only in human memory.**
## Clone This Workbench to Another Linux Machine
Register the MCP server with OpenCode:
```json
{
"mcp": {
"opencode-workbench": {
"type": "local",
"command": ["npx", "-y", "@simonmak-ascent/opencode-workbench"],
"enabled": true,
"timeout": 600000
}
}
}
```
Then ask the agent to run `inspect_target` → `plan_clone` → `apply_clone { confirm: true }` → `verify_clone`, for `{ "mode": "local" }` or `{ "mode": "ssh", "host": "<your-box>", "user": "<your-user>" }`. `apply_clone` is consent-gated: without `confirm:true` it returns a plan (components + privileged-command preview) and changes nothing. Run `list_required_credentials` to see which keys the box still needs and how to acquire them, and `bash scripts/selftest/run-selftest.sh` to verify it works. See [`mcp-server/README.md`](mcp-server/README.md) and [`docs/architecture/clone-mcp.md`](docs/architecture/clone-mcp.md).
The clone is **key-resilient**: with no model key it still boots on the OpenCode Zen free floor, and MCP servers whose credentials are absent are disabled and reported (not left to fail at runtime).
The connector never reads or transmits secret values; it writes an empty `~/.env.workbench` template for you to fill in.
## Quick Start
```bash
# Create a new build box
gh SWAS create --repo simonmak-ascent/opencode-workbench --machine basicLinux32gb
# Wait for postCreate (3-5 min) — installs everything automatically
# Then start coding:
opencode
```
## Architecture
```
opencode-workbench/
├── mcp-server/ # opencode-workbench: clone this profile onto Linux
│ ├── src/ # inspect / plan / apply / verify, local + SSH
│ ├── test/ # unit tests (vitest)
│ └── README.md
├── connector.json # MCP connector manifest / registration snippet
├── plugins/ # memory.ts + doc-tools.ts OpenCode plugins
├── package.json # thin launcher for opencode-workbench (bin + prepare)
├── .devcontainer/ # build box definition & bootstrap
│ ├── devcontainer.json # Container image, features, ports, remoteEnv
│ ├── setup.sh # Post-create: installs opencode, MCPs, Docker infra
│ └── aliases.sh # Shell aliases sourced at runtime
├── .opencode/
│ └── skills/ # 28 custom agent skills (10 research, 10 dev, 8 publishing)
├── vendor/ # Vendored MCP source code
│ ├── perplexity-agent-mcp/
│ └── browserless-mcp/
├── configs/ # Reference configurations
│ ├── mcp/ # MCP server inventory & architecture
│ ├── opencode/ # OpenCode settings documentation
│ ├── shell/ # Shell configuration
│ ├── git/ # Git configuration & hooks
│ └── providers/ # AI provider configuration
├── docs/ # Complete documentation system
│ ├── WORKBENCH_CHARTER.md # Governance: mission, principles, requirements
│ ├── security-model.md # Security architecture & threat model
│ ├── IMPROVEMENT_BACKLOG.md # Tracked improvements and fixes
│ ├── CHANGELOG_WORKBENCH.md # Append-only change history
│ ├── architecture/ # System documentation (incl. clone-mcp.md)
│ ├── recovery/ # Recovery procedures (4 docs)
│ ├── prompts/ # Operational prompt library (9 prompts)
│ └── backup-reports/ # Dated backup snapshots
├── scripts/ # Automation scripts
│ ├── backup/ # Master backup script
│ ├── inventory/ # Auto-generate inventories (software, env, MCP, OpenCode)
│ ├── security/ # Secret pattern scanner
│ ├── recovery/ # Recovery validation
│ └── maintenance/ # Config sync, routine tasks
├── .github/workflows/ # CI (docs, inventory, gitleaks, mcp-server)
├── opencode.json # OpenCode configuration (MCP servers)
├── AGENTS.md # OpenCode agent instructions
└── README.md # This file
```
## What's Inside
| Category | Details |
|----------|---------|
| **OpenCode** | Latest stable CLI, DeepSeek V4 Pro model, LSP enabled |
| **MCP Servers** | 35 configured (33 enabled, 2 disabled), 9 remote + 26 local |
| **Agent Skills** | 45 reusable skills in `.opencode/skills/` |
| **Infrastructure** | PostgreSQL 16 (Docker), Browserless Chromium (Docker) |
| **Tools** | pandoc, jq, miller, sqlite3, GitHub CLI, Playwright Chromium |
| **Prompts** | 9 operational prompts in `docs/prompts/` |
## Workstation Governance
This workstation operates under a formal charter. Key principles:
- **Single Source of Truth**: Runtime must match repository. Drift is a bug.
- **Secrets Never Touch Disk**: All secrets flow through the build box Secrets.
- **Immutable History**: Changelog is append-only. Every change is traceable.
- **Documentation Lives With Code**: Docs describe the system as it is, not as imagined.
Read the full charter: [`docs/WORKBENCH_CHARTER.md`](docs/WORKBENCH_CHARTER.md)
## Backup Workflow
```bash
# Master backup — full inventory, security scan, commit prep
bash scripts/backup/run-master-backup.sh
# Quick backup — save state before risky operations
bash scripts/maintenance/sync-runtime-config.sh && \
git diff > /tmp/quick-backup-$(date +%Y%m%d).diff
```
Or use OpenCode prompts:
- `docs/prompts/RUN_MASTER_BACKUP.md` — execute backup via AI
- `docs/prompts/QUICK_BACKUP.md` — rapid state preservation
## Recovery Workflow
Assume the build box is deleted. Only Git repo + build box Secrets survive.
```bash
# 1. Create new build box
gh SWAS create --repo simonmak-ascent/opencode-workbench --machine basicLinux32gb
# 2. Wait for automation (3-5 min)
# 3. If needed (usually done by setup.sh):
npx playwright install chromium
# Vercel MCP uses VERCEL_ACCESS_TOKEN (token auth — no OAuth step)
# 4. Validate recovery
bash scripts/recovery/validate-recovery.sh
```
Full details: [`docs/recovery/RECOVERY_PLAYBOOK.md`](docs/recovery/RECOVERY_PLAYBOOK.md)
## MCP Architecture
| Type | Count | Notes |
|------|-------|-------|
| Remote | 9 | context7, gh_grep, vdd, exa, cloudflare, clerk, vercel (token auth), sentry, stripe |
| Local | 26 | npm / vendored / binary stdio servers |
Totals: **35 configured** (33 enabled, 2 disabled: `google-search`, `google-workspace`).
See: [`docs/architecture/mcp-inventory.md`](docs/architecture/mcp-inventory.md)
## Secrets Management
All secrets stored in the build box Secrets. Never in repository files.
| # | Secret | Used By |
|---|--------|---------|
| 1 | `DEEPSEEK_API_KEY` | OpenCode (primary model) |
| 2 | `OPENCODE_API_KEY` | OpenCode Zen / Console Go providers |
| 3 | `SIMONMAK_ASCENT_PAT` | GitHub MCP, shadcn MCP, `gh` |
| 4 | `PERPLEXITY_API_KEY` | Perplexity MCP |
| 5 | `BRAVE_API_KEY` | Brave Search MCP |
| 6 | `BROWSERLESS_TOKEN` | Browserless MCP + container |
| 7 | `SENTRY_AUTH_TOKEN` | Sentry MCP |
| 8 | `VERCEL_ACCESS_TOKEN` | Vercel MCP (token auth) |
Additional keys for opt-in servers (`EXA_API_KEY`, `CLOUDFLARE_API_TOKEN`,
`STRIPE_SECRET_KEY`, `SURREAL_*`, `ALIBABA_CLOUD_*`, `AZURE_*`, `FIRECRAWL_API_KEY`,
`FRED_API_KEY`, `COMPANIES_HOUSE_API_KEY`) are catalogued in
[`docs/architecture/secrets.md`](docsLo que la gente pregunta sobre opencode-workbench
¿Qué es simonmak-ascent/opencode-workbench?
+
simonmak-ascent/opencode-workbench es mcp servers para el ecosistema de Claude AI. OpenCode Workbench: a reproducible, self-documenting, recoverable OpenCode development workstation — configuration, agent skills, MCP stack, and a clone MCP server for any Linux box Tiene 0 estrellas en GitHub y su última actualización registrada es del 2026-10-03.
¿Cómo se instala opencode-workbench?
+
Puedes instalar opencode-workbench clonando el repositorio (https://github.com/simonmak-ascent/opencode-workbench) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.
¿Es seguro usar simonmak-ascent/opencode-workbench?
+
Nuestro agente de seguridad ha analizado simonmak-ascent/opencode-workbench y le ha asignado un Trust Score de 95/100 (tier: Verified). Revisa el desglose completo de comprobaciones superadas y flags en esta página.
¿Quién mantiene simonmak-ascent/opencode-workbench?
+
simonmak-ascent/opencode-workbench es mantenido por simonmak-ascent. La última actividad registrada en GitHub es del 2026-10-03, con 0 issues abiertos.
¿Hay alternativas a opencode-workbench?
+
Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.
Despliega opencode-workbench en tu cloud
Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.
¿Mantienes este repo? Añade un badge a tu README
Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.
[](https://claudewave.com/repo/simonmak-ascent-opencode-workbench)<a href="https://claudewave.com/repo/simonmak-ascent-opencode-workbench"><img src="https://claudewave.com/api/badge/simonmak-ascent-opencode-workbench" alt="Featured on ClaudeWave: simonmak-ascent/opencode-workbench" width="320" height="64" /></a>Más MCP Servers
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
An open-source AI agent that brings the power of Gemini directly into your terminal.
Real-time global intelligence dashboard. AI-powered news aggregation, geopolitical monitoring, and infrastructure tracking in a unified situational awareness interface
🕷️ An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
The fastest path to AI-powered full stack observability, even for lean teams.