Opencode Workbench
Provision an OpenCode workbench and MCP stack on any Linux box, local or over SSH.
Connect it
Settings → Connectors → Add custom connector
URL: https://opencode-workbench.simonmak.com/mcpSettings → Apps & Connectors → Advanced → Developer mode
Create connector with URL: https://opencode-workbench.simonmak.com/mcp{
"mcpServers": {
"opencode-workbench": {
"url": "https://opencode-workbench.simonmak.com/mcp"
}
}
}claude mcp add --transport http opencode-workbench https://opencode-workbench.simonmak.com/mcp{
"servers": {
"opencode-workbench": {
"type": "http",
"url": "https://opencode-workbench.simonmak.com/mcp"
}
}
}{
"mcpServers": {
"opencode-workbench": {
"command": "npx",
"args": [
"-y",
"@simonmak-ascent/opencode-workbench@4.0.2"
]
}
}
}claude mcp add opencode-workbench -- npx -y @simonmak-ascent/opencode-workbench@4.0.210 tools, verified live
describe_workbenchread-onlyDescribe 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 avai
inspect_targetread-onlyProbe 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, an
plan_cloneread-onlyReturn 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
apply_clonecan modifyApply 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
verify_cloneread-onlyRe-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
install_componentcan modifyInstall 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 retu
remove_componentcan modifyUninstall 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/
update_componentcan modifyUpdate 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
list_required_credentialsread-onlyList 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 a
run_auth_flowread-onlyReturn 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 sema
Alternatives in Developer Tools
Compare →RRReactive ResumeA
Free open-source resume builder with remote MCP tools for resumes and job applications.
PAPg AiguideA
Comprehensive PostgreSQL documentation and best practices, including ecosystem tools
COContrastAPIA
55 tools, 7 Resources, Sigma rules, email SPF/DMARC, MITRE, CVE/KEV, risk_score. No key.
QRQR RápidoA
Generate QR codes for URLs, PIX, Wi-Fi, vCards, WhatsApp and more. For AI agents.
ZTZoom Team ChatOfficialA
Zoom Chat server for channels, messages, contacts, files, and chat collaboration.
ZTZoom TasksOfficialA
Zoom Tasks server for creating, updating, assigning, and synchronizing task workflows.