opencode-workbench

Name: opencode-workbench
Author: simonmak-ascent

MCP serverMCP

Provision an OpenCode workbench and MCP stack on any Linux box, local or over SSH.

by simonmak-ascentrepository ↗v4.0.1

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"opencode-workbench","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability18/18 checks ok

30 days ago

when	check	result	http	latency	detail
3 h ago	mcp initialize	ok	200	153 ms	server opencode-workbench 4.0.1 · protocol 2025-06-18 · 10 tools
10 h ago	mcp initialize	ok	200	144 ms	server opencode-workbench 4.0.1 · protocol 2025-06-18 · 10 tools
17 h ago	mcp initialize	ok	200	260 ms	server opencode-workbench 4.0.1 · protocol 2025-06-18 · 10 tools
23 h ago	mcp initialize	ok	200	159 ms	server opencode-workbench 4.0.1 · protocol 2025-06-18 · 10 tools
29 h ago	mcp initialize	ok	200	157 ms	server opencode-workbench 4.0.1 · protocol 2025-06-18 · 10 tools
35 h ago	mcp initialize	ok	200	339 ms	server opencode-workbench 4.0.1 · protocol 2025-06-18 · 10 tools
2 d ago	mcp initialize	ok	200	159 ms	server opencode-workbench 4.0.1 · protocol 2025-06-18 · 10 tools
2 d ago	mcp initialize	ok	200	171 ms	server opencode-workbench 4.0.1 · protocol 2025-06-18 · 10 tools
2 d ago	mcp initialize	ok	200	171 ms	server opencode-workbench 4.0.1 · protocol 2025-06-18 · 10 tools
2 d ago	mcp initialize	ok	200	158 ms	server opencode-workbench 4.0.1 · protocol 2025-06-18 · 10 tools

Tools observed via MCP handshake

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
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,
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 t
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).
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 idempo
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. Overw
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. `o
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
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
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`, `op

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.simonmak-ascent/opencode-workbench

first seen 5 d ago · fetched 2 d agoopen ↗

Field history (6 recent events)

5 d ago · declared · summary → "Provision an OpenCode workbench and MCP stack on any Linux box, local or over SSH."
5 d ago · declared · description → "Provision an OpenCode workbench and MCP stack on any Linux box, local or over SSH."
5 d ago · declared · publisherName → "simonmak-ascent"
5 d ago · declared · repoUrl → "https://github.com/simonmak-ascent/opencode-workbench"
5 d ago · declared · version → "4.0.1"
5 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from