Skip to main content
Glama
DeployFaith

hermes-gpt

by DeployFaith
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to hermes-gpt

No user-submitted related servers found.

    Related Servers

    • hermes-agent-mcp

      woonyong-choi
      A
      license
      B
      quality
      A
      maintenance
      Operates a local Hermes Agent install from any MCP client over stdio, enabling task delegation, cron management, config changes, gateway restarts, health checks, and skill or session inspection without exposing the agent to the network.
      16
      MIT

    • litellm-mcp

      nikitatsym
      A
      license
      A
      quality
      A
      maintenance
      MCP server for the LiteLLM proxy, enabling agents to administer resources like keys, teams, users, models, and proxy settings through risk-graded meta-tools.
      6
      MIT

    • hermes-mcp-remote

      kevincolten
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables controlling a Hermes Agent instance from any MCP client, exposing a broad set of Hermes CLI operations over MCP Streamable HTTP with bearer auth.
      MIT

    • hermes-mcp

      Stratfiy
      F
      license
      A
      quality
      C
      maintenance
      MCP server for controlling a Hermes agent deployment via its HTTP API, enabling health checks, log retrieval, task management, and deployment configuration from MCP clients.
      17
      -

    • Hermes Toolkit MCP

      hermegeddon
      A
      license
      B
      quality
      C
      maintenance
      A safety-first MCP operations cockpit for Hermes Agent installations, exposing typed, evidence-producing management primitives.
      73
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2/5.0

    Scored across 43 tools

    Disambiguation5/5

    Each tool name follows a distinct 'resource_action' pattern, making their purposes clear despite most descriptions being empty. For example, 'hermes_cron_list' vs 'hermes_cron_run' are unambiguous.

    Naming Consistency5/5

    All 43 tools use the consistent pattern 'hermes_<category>_<action>', with verbs in imperative form and underscores separating multi-word actions. No mixing of conventions.

    Tool Count2/5

    With 43 tools, the server is overloaded. While each category has multiple tools, the overall count exceeds the typical well-scoped range, making it difficult for agents to navigate.

    Completeness3/5

    The tool surface covers many aspects (config, cron, env, skills, etc.) but has notable gaps like missing CRUD for cron (no create/delete) and environment (no create/delete), leaving agents without complete lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources