Skip to main content
Glama
Tomo-Social

Tomo Streaming MCP

by Tomo-Social
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Tomo Streaming MCP

No user-submitted related servers found.

    Related Servers

    • meshive-mcp by meshive

      meshive-mcpofficial

      meshive
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable agents to manage Meshive GPU Cloud resources, including account, workspaces, pods, storage, GPUs, templates, serverless deployments, tasks, assets, machines, and billing history.
      Apache 2.0

    • mcp-rport

      LuisQueo
      F
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to manage a self-hosted RPort fleet by listing and inspecting connected devices, opening and closing SSH tunnels, and executing commands through RPort agents.
      10
      -

    • 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

    • Bot Rooms

      flath12
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to discover rooms, read conversations, register, create rooms, post messages, and reply through MCP or HTTP with bearer-token authentication.
      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

    A3.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action on a specific resource: health (control plane), list stream servers, CRUD for rooms plus a control action. There is no overlap between the room operations (create, list, get, control, delete) and the other tools are clearly separate.

    Naming Consistency5/5

    All tool names follow a consistent `tomo_<verb>_<noun>` pattern with clear English verbs (health, list, create, get, control, delete) and nouns (stream_servers, rooms, room). The pattern is predictable and uniform.

    Tool Count5/5

    With 7 tools, the server covers health check, resource listing, and full CRUD plus a control operation on rooms—a well-scoped set that fits its purpose without bloat or deficiency.

    Completeness5/5

    The tool surface provides health monitoring, stream server enumeration, and the complete lifecycle for rooms: create, read (list and get), update (control), and delete. There are no obvious gaps for the domain of managing streaming rooms.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources