opencode-workbench
This MCP server provisions, inspects, and manages the OpenCode Workbench development workstation on local or SSH Linux targets.
Describe the workbench: returns repository info, default components, component tiers, and optional MCP add-ons without touching a target.
Inspect a target: probes local or SSH Linux machines for OS, architecture, package manager, toolchain, Docker, OpenCode, and credential-name presence.
Plan a clone: previews install/present/manual component actions and privileged commands before changes.
Apply a clone: consent-gated, idempotent installation of the profile, OpenCode config, components, and a names-only
~/.env.workbenchtemplate.Verify a clone: checks per-component presence plus whether
opencode.jsonand~/.env.workbenchexist.Manage components: install, remove, or update individual Workbench components by id, with consent gating and dry-run/preview support.
List credentials: reports required credential names, which are present/missing, and how to acquire them without reading secret values.
Guide credential acquisition: returns provider URL, command, method, and next steps for one credential at a time.
Operate locally or over SSH: supports both
localandsshtarget modes for all target-operating tools.
Provides access to Brave Search via the Brave Search MCP, enabling web search capabilities for AI agents.
Integrates with Clerk via an MCP server for managing authentication and user management.
Integrates with Cloudflare via an MCP server for managing Cloudflare services and resources.
Uses Docker to run infrastructure components such as PostgreSQL 16 and Browserless Chromium for the workstation.
Integrates with GitHub via the GitHub MCP, enabling repository and workflow interactions using a GitHub PAT.
Uses npm to manage and launch MCP servers, including the opencode-workbench server via npx.
Integrates with Perplexity via the Perplexity MCP for AI-powered search and research capabilities.
Runs PostgreSQL 16 in Docker as part of the workstation infrastructure for data storage and management.
Integrates with Sentry via the Sentry MCP for error tracking and monitoring using a Sentry auth token.
Integrates with Stripe via the Stripe MCP for payment processing and management.
Integrates with Vercel via the Vercel MCP using token authentication for deployment and project management.
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).
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.
Related MCP server: CatHub Nyaanes
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:
opencodeArchitecture
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 credentialsMCP 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 fileWhat's Inside
Category | Details |
OpenCode | OpenCode 2 CLI, installed from the v2 channel (latest 2.x at clone time; |
MCP Servers | 31 configured (29 enabled, 2 disabled), 8 remote + 23 local |
Agent Skills | 76 reusable skills in |
Versions |
|
Infrastructure | PostgreSQL 16 (Docker), Browserless Chromium (Docker) |
Tools | pandoc, jq, miller, sqlite3, GitHub CLI, Playwright Chromium |
Prompts | 9 operational prompts in |
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).diffOr 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.shFull 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 |
| OpenCode (primary model) |
2 |
| OpenCode Zen / Console Go providers |
3 |
| GitHub MCP, shadcn MCP, |
4 |
| Perplexity MCP |
5 |
| Brave Search MCP |
6 |
| Browserless MCP + container |
7 |
| Sentry MCP |
8 |
| 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 |
| Mission, principles, governance |
| Security architecture, threat model, incident response |
| Tracked improvements and technical debt |
| Complete change history |
| System documentation (10 inventory docs) |
| Recovery playbook, disaster recovery, checklist, gap analysis |
| 9 operational prompts with index |
| Dated backup snapshots |
Adding to the Workbench
MCP Server: Add npm package to
.devcontainer/setup.sh, add toopencode.json, document indocs/architecture/mcp-inventory.mdAgent Skill: Create
.opencode/skills/<name>/SKILL.md, follow naming conventionTool: Add to
scripts/bootstrap-tools.shPrompt: Create in
docs/prompts/, updateprompt-index.mdAfter 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 docsLicense
MIT — see LICENSE.
A tool by Simon Mak.
If this saves you time, a ⭐ on GitHub helps others find it.
Available Tools
10 toolsapply_cloneApply a Workbench cloneADestructiveIdempotentInspect
Apply the Workbench profile to a target: clone the repo and install missing components (OpenCode CLI, Node/pnpm, MCP servers, skills, plugins, optional Docker). It OVERWRITES <home>/.config/opencode/opencode.json, copies AGENTS.md, resets an existing profile repo to origin/main, and runs global installs that need write permission (plus SSH for mode:ssh) and can take minutes. Writes a names-only ~/.env.workbench (mode 600); never secret values. Consent-gated and idempotent: without confirm:true it returns the plan and changes nothing. Parameter semantics: components defaults to required+core; workspace defaults to ~/opencode-workbench; skipRepo skips the clone/update; profileUrl overrides the git remote; dryRun returns the plan. To preview only, use plan_clone.
Inputs: target (required), dryRun, confirm, skipRepo, +3 more. Returns: plan, model, dryRun, target, +9 more
describe_workbenchWorkbench server infoARead-onlyIdempotentInspect
Describe this MCP server from its bundled profile without contacting any target or making a network call: repository URL, the default component set, components grouped by tier (required/core/optional), and optional MCP add-ons. It takes no parameters, is always safe, and returns instantly. Use it first to resolve a component id for install_component/remove_component/update_component or to see available add-ons; use inspect_target for a machine's live state.
Inputs: no named parameters. Returns: repo, repoGit, components, optionalMcp, +2 more
inspect_targetInspect a Linux targetARead-onlyIdempotentInspect
Probe one Linux machine — this host (local) or a remote host over SSH (ssh) — and report its OS, kernel, architecture, package manager, Node/npm, OpenCode, Docker, and per-tool detection flags, plus the names (never values) of credentials present. Read-only: it runs one shell probe as the target user (over SSH when mode:ssh), installs nothing, writes nothing, contacts no external service, and can take a few seconds per hop. Parameter semantics: target.mode selects local vs ssh (default local); target.host is required only for ssh; target.user defaults to the ssh config/current user; target.cwd sets the directory for relative checks; target.port/identityFile pass straight to ssh. Use it to see what a clone would touch, then plan_clone to turn that into an ordered plan and apply_clone to perform it.
Inputs: target (required). Returns: has, arch, home, osId, +12 more
install_componentInstall one Workbench componentADestructiveIdempotentInspect
Install a single Workbench component by id (e.g. node, opencode, npm-mcps, skills) on a target; component must be an id from describe_workbench. Overwrites that component's files when present (e.g. skills/plugins replace the copies under <home>/.config/opencode); global installs need write permission and can take minutes. Idempotent and consent-gated: without confirm:true it returns the plan. Parameter semantics: component is required; workspace defaults to ~/opencode-workbench; confirm defaults to false (plan only). Use it for one targeted component; use apply_clone to install the full default set.
Inputs: target (required), component (required), confirm, workspace. Returns: plan, model, dryRun, target, +9 more
list_required_credentialsList required credentialsARead-onlyIdempotentInspect
List the credentials the profile references, which the target already provides, and how to acquire each missing one. Value-blind: it reads only whether each env var is set — no values, no network, no writes — via one read-only probe. Parameter semantics: target selects the machine (local or SSH) and its home sets the returned template path and the env file the presence check reads; there are no other parameters. Returns present/missing var-name arrays plus one guidance record per credential (var, purpose, url, method, command). Use it after plan_clone to see what would degrade; act on one credential with run_auth_flow.
Inputs: target (required). Returns: target, missing, present, template, +1 more
plan_clonePlan a Workbench cloneARead-onlyIdempotentInspect
Return a read-only plan for a target: compare it against the Workbench profile and list each component as install, present, or manual, with the commands that would run. It still runs a detection probe on the target (same access as inspect_target) but clones nothing and writes nothing. Parameter semantics: components restricts the diff to those ids (default: required+core); workspace sets the expected profile path on the target (default ~/opencode-workbench); profileUrl overrides the git remote. Use it to preview before apply_clone, which performs the changes.
Inputs: target (required), dryRun, skipRepo, workspace, +2 more. Returns: steps, target, inspect, toInstall
remove_componentRemove one Workbench componentADestructiveIdempotentInspect
Uninstall one Workbench component by id from a target — the inverse of install_component — for a bounded, documented subset with an automated uninstall (e.g. opencode, pnpm, npm-mcps, skills, docker-containers); component must be an id from describe_workbench. Idempotent: an already-absent component reports absent; a component with no automated uninstall (system packages such as git/curl/node) reports manual. Destructive and consent-gated: without confirm:true it returns a preview and changes nothing, and it deletes only that component's files — never opencode.json or the profile repo. Parameter semantics: workspace sets the profile path some removals need; dryRun reports without changing. Use it to tear down one component; for several, call it per id.
Inputs: target (required), component (required), dryRun, confirm, +1 more. Returns: id, code, action, output, +2 more
run_auth_flowAcquire one credential (best-effort)ARead-onlyIdempotentInspect
Return the acquisition plan for one credential on a target: the provider URL, the exact non-interactive command when one exists (e.g. opencode auth login, opencode mcp auth vercel, gh auth login), and whether it is already present. Read-only and value-blind: it emits guidance and re-checks presence with one read-only probe; it does not run the commands or handle secret values. Parameter semantics: var must be an env var name returned by list_required_credentials (unknown names error); target selects the machine and its home is where the value should be written. Use it for a single credential; it does not replace that listing.
Inputs: var (required), target (required). Returns: url, var, next, method, +4 more
update_componentUpdate one Workbench componentADestructiveIdempotentInspect
Update one Workbench component in place by id: re-run its install script to fetch the current version (e.g. opencode re-runs the official installer; npm-mcps reinstalls the latest globals). It OVERWRITES the component's files, needs write permission, and can take minutes for global installs; the resolved version may change. Parameter semantics: component must be an id from describe_workbench; workspace defaults to ~/opencode-workbench; dryRun previews; confirm defaults to false — set confirm:true to apply. For the whole profile use apply_clone.
Inputs: target (required), component (required), dryRun, confirm, +1 more. Returns: id, code, action, output, +2 more
verify_cloneVerify a Workbench cloneARead-onlyIdempotentInspect
Re-check a target after a clone: return a per-component present/missing list plus whether opencode.json and ~/.env.workbench exist. Read-only and idempotent: it runs a detection probe (SSH or local) and checks files, writing nothing. target selects the machine (local or SSH) and its home is where the opencode.json and ~/.env.workbench checks run; components restricts the check to those ids (omit it to check every component, the default); workspace sets the profile path used by component checks. Use it after apply_clone and after component changes; for a pre-clone preview use plan_clone.
Inputs: target (required), dryRun, skipRepo, workspace, +2 more. Returns: target, missing, envExists, components, +1 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Most tools have clearly distinct purposes, and the descriptions explicitly cross-reference each other (inspect_target for live state, plan_clone for a diff plan, verify_clone for post-clone re-check). The three read-only probe tools (inspect_target, plan_clone, verify_clone) overlap somewhat and require careful reading to separate, but the descriptions do enough to guide selection.
Every tool follows a consistent snake_case verb_noun pattern: verify_clone, describe_workbench, inspect_target, plan_clone, apply_clone, install_component, remove_component, update_component, list_required_credentials, run_auth_flow. The component lifecycle (install/remove/update) is especially clean and predictable.
Ten tools is well-scoped for a workbench provisioning/profiling server. Each tool earns its place, covering the full flow from describe and inspect through plan, apply, verify, per-component management, and credentials.
The surface covers the full lifecycle: describe, inspect, plan, apply, verify, plus per-component install/remove/update and credential discovery/auth guidance. Coverage is strong; the only minor gap is the deliberate absence of any secret-value handling, which is an intentional design constraint rather than an oversight.
Maintenance
Related MCP Connectors
Work on your own computers from Claude or ChatGPT: run commands, edit and search files.
Connect ChatGPT and Claude to your Mac, Windows or Linux with secure MCP remote access.
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
Remote Linux boxes for coding agents: Docker, a browser, screenshots, logs, human takeover.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceExposes local OpenCode instances as remote MCP servers for Claude and ChatGPT, enabling terminal access, session management, and interactive human-in-the-loop workflows. It simplifies deployment for local machines using Cloudflare Tunnels to provide secure public connectivity and OAuth support.-
- AlicenseNot gradedqualityCmaintenanceEnables orchestrating multiple AI CLI agents (Codex, Grok, Claude, etc.) via Claude Code, providing tools for dispatching tasks, broadcasting, debating, and managing jobs through a local MCP server.MIT

2ools MCP Serverofficial
AlicenseAqualityCmaintenanceRemote MCP server for 2ools—build, version, review, and export websites, web apps, and games from the AI chat you already use. This repository includes a credential-free stdio proxy and Dockerfile that forward introspection to the verified remote endpoint without mocking tools.431MIT- AlicenseNot gradedqualityBmaintenanceSpins up isolated opencode instances in Docker containers as MCP servers, providing 80 tools for file and shell operations within a scoped workspace without exposing the host filesystem.458 npmMIT