Skip to main content
Glama
PerssonaOps

@perssona/orchestrator

Official
by PerssonaOps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to @perssona/orchestrator

No user-submitted related servers found.

    Related Servers

    • terminal-bridge-mcp

      dividduang
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that bridges AI assistants to real terminal sessions, enabling creation, management, and interaction with persistent PTY processes for running commands, monitoring output, and debugging.
      1
      MIT

    • ainpcengine

      jyswee
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for creating, managing, and interacting with AI-powered NPCs with persistent memory, supporting dialogue, game events, and persona generation for coding agents.
      39 npm
      1
      -

    • Combined MCP Server

      SMH01-MOD-NEXT
      A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted MCP server that gives AI agents controlled access to a machine: filesystem, shell, background processes, git, web fetching and persistent key-value memory.
      GPL 3.0
    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

    B3.3/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some overlap among the various 'create' tools (e.g., create_agent_pair, create_claude_terminal_from_agent, create_connected_terminal) that could cause confusion if descriptions are not read carefully. However, descriptions are clear enough to differentiate them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (e.g., add_node_to_grid, connect_nodes, run_workflow_from_annotation). No mixing of conventions or inconsistent styles.

    Tool Count4/5

    With 20 tools, the server covers a broad canvas orchestration domain including node management, connections, terminals, and workflows. While on the higher side, each tool serves a specific purpose and the count feels justified.

    Completeness4/5

    The tool set covers core operations: CRUD for annotation nodes, connections, terminals, grid management, and workflow execution. Minor gaps exist (e.g., no direct update for non-annotation nodes, no node renaming), but the surface is largely complete for its stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources