Skip to main content
Glama

Related Servers

Alternatives to opencode-workbench

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Exposes local OpenCode instances as remote MCP servers for Claude and ChatGPT, enabling terminal access, session management, and interactive human-in-the-loop workflows. It simplifies deployment for local machines using Cloudflare Tunnels to provide secure public connectivity and OAuth support.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects MCP clients such as Claude, Cursor, and VS Code to OpenCode's headless API so users can delegate coding work — asking questions, implementing features, monitoring background jobs, answering prompts and permission requests, and reviewing changes across multiple projects. Supports synchronous runs, asynchronous jobs with polling and recovery, multi-project directory scoping, and configurable server authentication and tool profiles.
      24,126 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes 20 tools over stdio that let coding agents treat any SSH-reachable machine as a local workspace: reading, writing, editing, searching and listing files, running commands and background jobs, driving persistent terminals, and forwarding ports over one pooled connection, with nothing installed on the remote host.
      270 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Spins up isolated opencode instances in Docker containers as MCP servers, providing 80 tools for file and shell operations within a scoped workspace without exposing the host filesystem.
      458 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables orchestrating multiple AI CLI agents (Codex, Grok, Claude, etc.) via Claude Code, providing tools for dispatching tasks, broadcasting, debating, and managing jobs through a local MCP server.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Remote MCP server for 2ools—build, version, review, and export websites, web apps, and games from the AI chat you already use. This repository includes a credential-free stdio proxy and Dockerfile that forward introspection to the verified remote endpoint without mocking tools.
      43
      1
      MIT

    TDQS

    A4.5/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, and the descriptions explicitly cross-reference each other (inspect_target for live state, plan_clone for a diff plan, verify_clone for post-clone re-check). The three read-only probe tools (inspect_target, plan_clone, verify_clone) overlap somewhat and require careful reading to separate, but the descriptions do enough to guide selection.

    Naming Consistency5/5

    Every tool follows a consistent snake_case verb_noun pattern: verify_clone, describe_workbench, inspect_target, plan_clone, apply_clone, install_component, remove_component, update_component, list_required_credentials, run_auth_flow. The component lifecycle (install/remove/update) is especially clean and predictable.

    Tool Count5/5

    Ten tools is well-scoped for a workbench provisioning/profiling server. Each tool earns its place, covering the full flow from describe and inspect through plan, apply, verify, per-component management, and credentials.

    Completeness4/5

    The surface covers the full lifecycle: describe, inspect, plan, apply, verify, plus per-component install/remove/update and credential discovery/auth guidance. Coverage is strong; the only minor gap is the deliberate absence of any secret-value handling, which is an intentional design constraint rather than an oversight.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues