Provision a reproducible OpenCode workstation on any Linux box.
opencode-workbench is an MCP server that turns a bare Linux machine — local or remote over SSH — into a ready OpenCode development workstation: it scans the platform, installs the latest stable OpenCode, applies the full profile (MCP servers, agent skills, plugins, config), and verifies the result. Secrets are never read, transmitted, or written.
npm Official MCP Registry Glama Context7 Streamable HTTP MIT
10 tools over one MCP surface
Read-only discovery and planning; consent-gated mutations; value-blind credential handling.
| Tool | What it does | Mode |
|---|---|---|
describe_workbench | Repo, components by tier, optional MCP add-ons. | read-only |
inspect_target | OS, kernel, arch, package manager, Node, Docker, OpenCode, credential names. | read-only |
plan_clone | Diff a target against the profile → install / present / manual steps. | read-only |
apply_clone | Clone the profile + install missing components; consent-gated. | mutating |
install_component | Install one component by id; consent-gated. | mutating |
remove_component | Uninstall one component by id (bounded subset); consent-gated. | mutating |
update_component | Update/upgrade one component in place; consent-gated. | mutating |
verify_clone | Re-check config, env template, and every component. | read-only |
list_required_credentials | Which credentials are missing and how to acquire each (value-blind). | read-only |
run_auth_flow | Emit-and-verify acquisition guidance for one credential. | read-only |
Quick start
1 · Local stdio
Run without installing, then point any MCP client at it.
npx -y @simonmak-ascent/opencode-workbench
2 · Remote (Streamable HTTP)
Use the hosted connector — no local install.
https://opencode-workbench.simonmak.com/mcp
Register with OpenCode (or any MCP client)
{
"mcp": {
"opencode-workbench": {
"type": "local",
"command": ["npx", "-y", "@simonmak-ascent/opencode-workbench"],
"enabled": true,
"timeout": 600000
}
}
}
Then drive a clone
describe_workbench → inspect_target → plan_clone → apply_clone { confirm: true } → verify_clone
Security posture
Secret-value-free
The connector never reads, transmits, or writes secret values. It writes an empty ~/.env.workbench (mode 600) listing only the variable names to fill in.
Consent-gated mutations
Every install/apply/remove/update returns a plan first; nothing changes until you pass confirm: true.
Value-blind credentials
Credential tools check only whether an env var is set and return acquisition guidance — never the value.
Scanned
The repository is public and gated by gitleaks and GitHub secret scanning on every push.
Where to find it
GitHub repository · npm package · Official MCP Registry · Glama · Context7