← All launches
0 Report

opencode-workbench

by FastDrop

MCP Verified yesterday Registry import free

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

Share

Provision an OpenCode workbench and MCP stack on any Linux box, local or over SSH. Official MCP Registry: io.github.simonmak-ascent/opencode-workbench@2.0.0. Remote endpoint: https://opencode-workbench.simonmak.com/mcp

Problem it solves

Discoverable MCP server listed in the official MCP Registry.

How it's different

Remote MCP endpoint ingested from the official registry and probed by FastDrop.

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as io.github.simonmak-ascent/opencode-workbench and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Claim this listing

Tools this endpoint exposes

Read directly from the endpoint on 2 Oct 2026. Not supplied by the maker.

  • get_workbench_info

    Describe this MCP server and its capabilities without contacting any target: repository URL, the default component set, components grouped by tier (required/core/optional), and optional MCP add-ons. R

  • 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, pl

  • plan_clone

    Compare a target against the portable Workbench profile and return each component as `install`, `present`, or `manual`, with privileged-command previews and the list to install. Read-only; installs no

  • apply_clone

    Install the Workbench profile on a target: clone the profile repo and install missing components (repo, OpenCode CLI, Node/pnpm, npm/vendored/research MCPs, skills, plugins, optional Docker), writing

  • verify_clone

    Re-check a target after a clone: confirm `opencode.json` and `~/.env.workbench` exist and re-detect every component, returning the missing list. Read-only; needs SSH for `mode: ssh`. Use it after appl

  • 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 get_workbench_info. Idempotent and consent-gated: without `confir

  • list_required_credentials

    List the credentials the profile references, which the target already provides, and how to acquire each missing one (label, purpose, provider URL, method, exact command). Value-blind: checks only whet

  • 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`

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.

Sign in to claim this listing

Reviews

Sign in to leave a review.

No reviews yet.

Comments

Sign in to join the discussion.

No comments yet - start the discussion.