Provisiona una estación de trabajo de desarrollo OpenCode reproducible y un stack de MCP en cualquier máquina Linux, ya sea de forma local o vía SSH.
También conocido como simonmak-ascent/opencode-workbench, @simonmak-ascent/opencode-workbench
- Stars
- 1
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 5.0.1
- Último commit
- 2 nov 2026
- Licencia
- MIT
¿Qué es opencode-workbench MCP?
opencode-workbench es un MCP server. Provisiona una estación de trabajo de desarrollo OpenCode reproducible y un stack de MCP en cualquier máquina Linux, ya sea de forma local o vía SSH.
Resumen generado a partir del README del proyecto
Acerca del MCP server de opencode-workbench
Los desarrolladores que busquen desplegar un entorno de desarrollo estandarizado y reproducible pueden usar esta herramienta para aprovisionar una estación de trabajo OpenCode completa en cualquier máquina Linux. Al ejecutar el servidor de forma local o vía SSH, puedes clonar un stack completo que incluye configuraciones de estación de trabajo específicas, 76 Agent Skills reutilizables y 31 MCP servers configurados. La configuración está diseñada para ser autodocumentada y recuperable, asegurando que tu entorno de desarrollo se mantenga consistente en diferentes hardware.
El proceso utiliza un ciclo de vida específico de descubrimiento, planificación y aplicación. Puedes usar herramientas como inspect_target para auditar una máquina, plan_clone para previsualizar cambios y apply_clone para ejecutar la instalación. El servidor está construido para ser resiliente a las claves, lo que significa que puede arrancar incluso sin las claves del modelo, y gestiona las credenciales escribiendo un archivo de plantilla en lugar de manejar valores sensibles directamente. Esto lo hace adecuado tanto para el desarrollo local como para la gestión de servidores remotos a través de SSH.
Qué puedes hacer con él
- 1Clonar una estación de trabajo a un servidor remotoAprovisiona un entorno de desarrollo OpenCode completo en una máquina Linux remota usando credenciales SSH.
- 2Auditar la preparación de una máquina objetivoInspecciona una máquina Linux para verificar su sistema operativo actual, el toolchain y la configuración de Docker antes del despliegue.
- 3Verificar la configuración exitosa del entornoEjecuta una comprobación de validación para asegurar que la estación de trabajo clonada sea totalmente funcional e identificar cualquier credencial faltante.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar opencode-workbench MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar opencode-workbench MCP en Claude Code
$ claude mcp add opencode-workbench -- npx -y @simonmak-ascent/opencode-workbenchInstalar opencode-workbench MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"opencode-workbench": {
"command": "npx",
"args": [
"-y",
"@simonmak-ascent/opencode-workbench"
]
}
}
}Instalar opencode-workbench MCP en VS Code
.vscode/mcp.json
{
"servers": {
"opencode-workbench": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@simonmak-ascent/opencode-workbench"
]
}
}
}Instalar opencode-workbench MCP en VS Code CLI
$ code --add-mcp '{"name":"opencode-workbench","type":"stdio","command":"npx","args":["-y","@simonmak-ascent/opencode-workbench"]}'Instalar opencode-workbench MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"opencode-workbench": {
"command": "npx",
"args": [
"-y",
"@simonmak-ascent/opencode-workbench"
]
}
}
}Instalar opencode-workbench MCP en Codex
$ codex mcp add opencode-workbench -- npx -y @simonmak-ascent/opencode-workbenchInstalar opencode-workbench MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.opencode-workbench] command = "npx" args = ["-y", "@simonmak-ascent/opencode-workbench"]
Instalar opencode-workbench MCP en Gemini CLI
$ gemini mcp add -s user opencode-workbench npx -- -y @simonmak-ascent/opencode-workbenchInstalar opencode-workbench MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"opencode-workbench": {
"command": "npx",
"args": [
"-y",
"@simonmak-ascent/opencode-workbench"
]
}
}
}Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesiblesimonmak-ascent/opencode-workbench is public and reachablegithub.com/simonmak-ascent/opencode-workbench ↗Aprobado
- El paquete indica este repositorio como su origenNo verificado
- Procedencia de la compilación (atestación de Sigstore)No build attestation published for this releaseNo verificado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-11-02github.com/simonmak-ascent/opencode-workbench ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from @simonmak-ascent/opencode-workbenchAprobado
- No hay avisos críticos en el paquete ni en sus dependencias100 resolved dependencies checked; no critical advisoryosv.dev ↗Aprobado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPinitialize answered with protocol 2025-06-18 in 150 msAprobado
README
Ver en GitHubOpenCode 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).
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 (76 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:
{
"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 and 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 (≤ 5 minutes)
Fastest path: no box required — register the MCP server with
npx -y @simonmak-ascent/opencode-workbench (config in
Clone This Workbench); or provision a fresh box:
# 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
flowchart TB
AGENT["OpenCode agent"] -->|"npx @simonmak-ascent/opencode-workbench"| MCP["opencode-workbench MCP<br/>inspect · plan · apply · verify"]
REPO[("Git repo — single source of truth")] --> MCP
MCP -->|"local or SSH"| BOX["Target Linux box"]
BOX --> PROF["Workstation profile<br/>OpenCode CLI · 31 MCP servers · 76 skills · Docker infra"]
Clone lifecycle
apply_clone is consent-gated: without confirm: true it returns a plan and changes nothing.
sequenceDiagram
autonumber
participant A as OpenCode agent
participant M as opencode-workbench MCP
participant B as Target box (local or SSH)
A->>M: inspect_target
M-->>A: OS, toolchain, Docker, existing config
A->>M: plan_clone
M-->>A: components + privileged-command preview
A->>M: apply_clone { confirm: true }
M->>B: install components · write ~/.env.workbench template
B-->>M: result
A->>M: verify_clone
M-->>A: pass/fail + missing credentials
MCP tool surface
flowchart LR
A["OpenCode agent"] --> D["Discovery<br/>describe_workbench · inspect_target"]
A --> C["Clone<br/>plan_clone · apply_clone · verify_clone"]
A --> K["Components<br/>install · remove · update_component"]
A --> S["Credentials<br/>list_required_credentials · run_auth_flow"]
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/ # 76 agent skills, one directory per SKILL.md
├── 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 | OpenCode 2 CLI, installed from the v2 channel (latest 2.x at clone time; inspect_target reports the version it found) · DeepSeek V4 Pro model · LSP enabled |
| MCP Servers | 31 configured (29 enabled, 2 disabled), 8 remote + 23 local |
| Agent Skills | 76 reusable skills in .opencode/skills/ |
| Versions | workbench.versions.json — every MCP server, plugin and skill resolved from its real upstream, regenerated and CI-checked |
| 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
Backup Workflow
# 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 AIdocs/prompts/QUICK_BACKUP.md— rapid state preservation
Recovery Workflow
Assume the build box is deleted. Only Git repo + build box Secrets survive.
# 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
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: 31 configured (29 enabled, 2 disabled: google-search, google-workspace).
See: 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 — never by value.
See: docs/architecture/secrets.md
Documentation Index
| Document | Purpose |
|---|---|
docs/WORKBENCH_CHARTER.md |
Mission, principles, governance |
docs/security-model.md |
Security architecture, threat model, incident response |
docs/IMPROVEMENT_BACKLOG.md |
Tracked improvements and technical debt |
docs/CHANGELOG_WORKBENCH.md |
Complete change history |
docs/architecture/ |
System documentation (10 inventory docs) |
docs/recovery/ |
Recovery playbook, disaster recovery, checklist, gap analysis |
docs/prompts/ |
9 operational prompts with index |
docs/backup-reports/ |
Dated backup snapshots |
Adding to the Workbench
- MCP Server: Add npm package to
.devcontainer/setup.sh, add toopencode.json, document indocs/architecture/mcp-inventory.md - Agent Skill: Create
.opencode/skills/<name>/SKILL.md, follow naming convention - Tool: Add to
scripts/bootstrap-tools.sh - Prompt: Create in
docs/prompts/, updateprompt-index.md - After any change: Update
CHANGELOG_WORKBENCH.md, run master backup
Recovery Score: 94/100
Validated disaster recovery within < 10 minutes using repository + build box Secrets alone.
Use with Context7
Up-to-date OpenCode Workbench documentation is indexed on Context7, so coding agents can pull it into context on demand. With the Context7 MCP server or ctx7 CLI installed, name the library in your prompt:
use library /simonmak-ascent/opencode-workbench for API and docs
License
MIT — see LICENSE.
A tool by Simon Mak.
If this saves you time, a ⭐ on GitHub helps others find it.
Preguntas sobre opencode-workbench MCP
¿Cómo agrego opencode-workbench MCP a Claude Code?
Ejecuta claude mcp add opencode-workbench -- npx -y @simonmak-ascent/opencode-workbench en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego opencode-workbench MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Cómo clono este workbench a otra máquina Linux?
Registra el MCP server con OpenCode y usa el agente para ejecutar la secuencia inspect_target, plan_clone, apply_clone y verify_clone.
¿Es seguro el proceso de clonación?
Sí, el comando apply_clone requiere consentimiento; solo devolverá un plan sin realizar cambios a menos que proporciones una confirmación explícita.
¿Cómo gestiona el servidor las credenciales sensibles?
El conector no lee ni transmite valores secretos; en su lugar, crea un archivo de plantilla vacío para que lo completes manualmente.