bots.st/opencode-workbench
opencode-workbench
Provision and manage an MCP workbench over SSH
851 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 10
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://opencode-workbench.simonmak.com/mcp - npm
npx -y @simonmak-ascent/opencode-workbenchReleased 29 Oct 2026, version 5.0.1
What it can do
| Tool | What it says it does |
|---|---|
apply_clone | 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… |
describe_workbench | 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… |
inspect_target | 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… |
install_component | 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… |
list_required_credentials | 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… |
plan_clone | 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… |
remove_component | 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… |
run_auth_flow | 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… |
update_component | 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… |
verify_clone | 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… |
In its maker's words
Provision an OpenCode workbench and MCP stack on any Linux box, local or over SSH.
- Source
- github.com/simonmak-ascent/opencode-workbench
- Publisher
- ascent-partners.com (8 listings in the registry)
- Listed from
- the official MCP Registry as
com.ascent-partners/opencode-workbench - Version
- 5.0.1, updated 29 Oct 2026
- Kinds of work
- Cloud and DevOps, Code and developer tools, AI models and agent tools
The domain it lives on
- simonmak.com
- registered 7 Jan 2026 (10 months ago), at GoDaddy.com, LLC, its name does not resolve now
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 851 ms | |
| Answered | 2063 ms | |
| Answered | 666 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.