Skip to main content
Glama
Sign In
ZCode MCP Server

ZCode MCP Server

by Mnehmos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to ZCode MCP Server

No user-submitted related servers found.

    Related Servers

    • dsh-zcode-bridge

      Sandyzzx
      A
      license
      A
      quality
      A
      maintenance
      Enables a DeepSeek Harness agent to delegate bounded coding tasks to a local ZCode runtime, follow their progress through events, and review the resulting diffs before accepting or continuing the work. It also exposes model catalog, default-model, and setup-diagnostics tools for managing those delegated tasks.
      12
      Apache 2.0

    • hands

      abhinavshyju
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable chat clients like ChatGPT, Claude, and Cursor to read, search, edit, and run commands on a local machine, including git operations and browser automation. Runs as a local daemon with workspace path jails, safety modes, checkpoints, and human-in-the-loop approval for edits and shell commands.
      MIT

    • glm-workflow-mcp

      JawadAhbab
      A
      license
      Not graded
      quality
      D
      maintenance
      Delegates autonomous coding tasks to Z.ai's GLM models with a genuine agent loop, file operations, and verification via git and real process results.
      41 npm
      MIT

    • Free Codin Agent

      office233
      A
      license
      C
      quality
      F
      maintenance
      This MCP server gives an AI coding host controlled, client-agnostic access to a local machine's developer capabilities: transactional file edits, shell and PTY execution, Git and project inspection, language-server operations, isolated browser automation, Windows UI automation, VS Code state, durable jobs, and checkpoints, all bounded by filesystem root allowlisting and resource admission controls. It speaks standard MCP over stdio, Streamable HTTP, and legacy HTTP+SSE, and can also run headless as a long-lived job runner without any hosted model vendor.
      114
      ISC

    • chatgpt-with-codex

      yuumiqwq
      A
      license
      Not graded
      quality
      B
      maintenance
      A local MCP bridge that lets ChatGPT chat mode operate the user's own computer, running project, file, and shell tasks through a local executor and returning progress and results to the conversation. It also coordinates Codex sessions (persistent or one-off) and other agent CLIs as sub-agents.
      MIT

    • gentle-terminal

      reyrodman
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to control real interactive shells, REPLs, and TUIs over stdio, supervise other agents, surface approval prompts, and verify outcomes without auto-approving or mistaking timeouts for success.
      1
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.5/5.0

    Scored across 14 tools

    Disambiguation4/5

    Each tool targets a distinct ZCode subsystem (status, session, chat, conversation, files, settings, plugins, MCP, automation, usage, models, approval, headless, protocol), limiting direct overlap. However, execution-related tools (zcode_chat, zcode_headless, zcode_automation, zcode_protocol) and read/analytics tools (zcode_conversation, zcode_usage) could be confused at a glance, so not entirely unambiguous.

    Naming Consistency5/5

    All 14 tools use the identical zcode_ snake_case prefix and noun-based naming pattern (zcode_status, zcode_session, etc.). No mixing of camelCase, verb styles, or other conventions.

    Tool Count5/5

    14 tools is within the well-scoped 3–15 range and matches the breadth of the ZCode platform. Each tool corresponds to a distinct subsystem rather than a trivial action, so the set is not bloated.

    Completeness4/5

    The surface covers core lifecycle and management areas: status, session, chat, conversation, files, settings, plugins, MCP, automation, usage, models, approval, headless, and raw protocol. Minor gaps remain—e.g., no explicit abort/cancel-turn operation and no direct file-read tool (an intentional architectural limitation)—so an agent may need workarounds for edge cases.

    Maintenance

    ActivityStale
    ResponsivenessOutdated data

    Resources