Skip to main content
Glama
kranz-org

Kranz MCP

by kranz-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Related Servers

Alternatives to Kranz MCP

No user-submitted related servers found.

    Related Servers

    • ForgeBridge

      t1ktakdev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables local, permissioned development workflows from compatible AI clients, including filesystem editing, interactive terminals, durable jobs, Git operations, and semantic browser testing.
      31 npm
      1
      Apache 2.0

    • worktree-switcher

      pioootrek
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to inspect projects, claim worktrees, and move or start dev servers without changing ports, while coordinating with human-owned locks.
      359 npm
      MIT

    • 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

    • Harbor MCP Server

      luke-fairbanks
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to discover, configure, and manage local development servers. Provides tools for app registration, port allocation, lifecycle control, and log access without manual config editing.
      124 npm
      MIT

    • web-gpt-agent-core

      dbc-hbin
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects ChatGPT Web to a local development environment, enabling file reads and patches, shell execution, plan updates, and isolated worktree coordination through permissioned MCP tools.
      3
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.1/5.0

    Scored across 25 tools

    Disambiguation4/5

    Each tool targets a distinct operational concept (runtime lifecycle vs service lifecycle vs actions vs logs), and descriptions clarify edge cases like up/down vs start/stop. Some adjacent tools (ports vs port_inspect, status vs health vs wait, runs vs action_result) could be initially confused but are distinguishable on reading.

    Naming Consistency3/5

    Names mix bare nouns (runtimes, status, logs), bare verbs (up, start, reload), and snake_case with resource prefixes (action_list, run_delete, logs_clear). The action_* family is consistent, but overall there is no single predictable verb_noun pattern. Still readable.

    Tool Count3/5

    25 tools is heavy for an MCP surface, but the domain spans runtime, services, actions, logs, ports, health, and configuration, so most tools correspond to real operations. Borderline over-scoped rather than redundant.

    Completeness4/5

    Operational lifecycle is well covered: runtime up/down, service start/stop/restart/status/health/wait, action run/cancel/result, logs query/clear, plan, graph, ports, doctor, reload, and run deletion. Missing are config-editing operations and possibly service-level env/secret management, but these may be out of scope.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources