Skip to main content
Glama
draygen

aion-mcp

by draygen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to aion-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-ssh-multi

      gilberth
      A
      license
      A
      quality
      B
      maintenance
      MCP server for managing multiple SSH servers via AI assistants, offering tools for remote command execution, file operations, and system monitoring.
      11
      12 PyPI
      1
      MIT

    • R-Shell

      MageGojo
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server enabling AI assistants to securely operate remote servers via persistent SSH sessions, with tools for command execution, file transfer, directory listing, and system monitoring.
      4
      MIT

    • open-ssh-mcp

      cjp1016
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for managing remote SSH servers, enabling AI agents to execute commands, transfer files, and perform deployment operations securely.
      MIT

    • sandbox-env-mcp

      hs3434
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing AI agents with persistent shells, filesystem access, and multi-machine management backed by Docker containers or remote SSH hosts.
      1
      AGPL 3.0

    • Simple SSH MCP Server

      bhayanak
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI assistants full SSH/SFTP remote operations — session management, command execution, interactive shells, file transfers, port forwarding, and system diagnostics.
      2
      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

    B3.3/5.0

    Scored across 45 tools

    Disambiguation2/5

    Several tools have overlapping purposes, notably memory_get_facts and aion_memory_browse both retrieve facts with category filters, and multiple query tools (aion_query, aion_api_chat, ollama_query, openai_query) send prompts to different backends but could confuse an agent. Most other tools are distinct, but this ambiguity is significant.

    Naming Consistency3/5

    Tool names generally follow a [domain]_[action] pattern with snake_case, but there are inconsistencies: memory_get_facts vs aion_memory_browse, aion_admin_profile_rebuild vs aion_admin_users, and some names are nouns (system_status) while others are verbs (fleet_run). The prefixes help but the pattern isn't uniform.

    Tool Count2/5

    45 tools is far above the typical 3-15 range, making the server unwieldy. While it covers many subdomains, the tool count is excessive and would benefit from splitting into focused servers.

    Completeness3/5

    The server covers a broad range of operations for AION memory, conversations, system health, and various services, but there are notable gaps such as no memory update, no conversation delete, and limited SonChat operations beyond invites. Core workflows are present, but the surface is uneven.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources