Skip to main content
Glama
DeployFaith

Hermes_WorldKit_MCP

by DeployFaith
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Hermes_WorldKit_MCP

No user-submitted related servers found.

    Related Servers

    • godot-mcp-lite

      baitang-bt
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a secure, authenticated MCP bridge to control a local Godot editor from Cursor, enabling scene/node management, script validation, editor diagnostics, and runtime inspection through a whitelisted set of tools.
      MIT

    • Godot Universal MCP

      Noa3
      A
      license
      B
      quality
      B
      maintenance
      Connects MCP-capable AI clients to a running Godot 4 editor for scene, node, project, and debug runtime operations via a local-first architecture.
      36
      1
      MIT

    • Godot AI

      hi-godot
      A
      license
      A
      quality
      A
      maintenance
      Connects MCP clients directly to a live Godot editor, enabling AI assistants to build scenes, edit nodes, and control the editor through over 120 operations.
      47
      21,410 PyPI
      2,918
      MIT

    • godot-mcp

      WindSeries83
      A
      license
      A
      quality
      B
      maintenance
      MCP bridge between an AI assistant and the Godot editor, enabling control via 6 tools (call methods, run GDScript, screenshots, etc.) over WebSocket.
      10
      3 npm
      1
      MIT

    • godot-mcp

      zbrkic
      A
      license
      C
      quality
      C
      maintenance
      Enables MCP clients to inspect, validate, test, export, and query Godot projects, including live state from an open editor via a bridge addon.
      20
      24 npm
      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

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool addresses a distinct concern: connection status, capability discovery, scene content, current selection, and changing selection. The two node-related tools are separated by summary versus selected state, and the action verb in select_node makes its purpose clear.

    Naming Consistency4/5

    All tools share a consistent worldkit_ prefix and snake_case style, which makes them predictable. However, most names are noun-like while select_node is the only verb-led name, so the pattern is not perfectly uniform.

    Tool Count5/5

    Five tools is a tight, well-scoped set for a safe editor bridge. Each tool covers a necessary operation without redundancy.

    Completeness4/5

    The surface covers the core read-only workflow: verify connection, discover capabilities, summarize the scene, inspect selected nodes, and change selection. Minor gaps like deselecting or retrieving a specific node's full details are absent but are not fatal for the apparent safe-introspection purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources