Skip to main content
Glama
6amdev

6amdev-server-mcp

Official
by 6amdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to 6amdev-server-mcp

No user-submitted related servers found.

    Related Servers

    • linux-mcp-server

      szoran53
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for managing Ubuntu/Linux systems, enabling AI assistants to execute commands, manage services, files, logs, and packages via local or SSH connection.
      -

    • AgenSysAdmin

      E13ctr0N
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for remote Linux server administration via SSH, integrating with Claude Code to manage Ubuntu/Debian servers.
      2
      -

    • linux-ssh-mcp

      JINDEZHIDIYE
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI assistants to manage SSH terminal sessions, execute commands, and automate server operations through natural language, with multi-tab support and session persistence.
      MIT

    • Athena MCP Server

      Kingdamienjl
      A
      license
      Not graded
      quality
      F
      maintenance
      A comprehensive MCP server integrating OpenAI GPT models for AI-powered tasks like code analysis, generation, and translation, along with system utilities, Docker management, network diagnostics, and web tools.
      MIT

    • R-Shell

      MageGojo
      A
      license
      Not graded
      quality
      A
      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
    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.1/5.0

    Scored across 34 tools

    Disambiguation4/5

    Tools are grouped by domain (system, docker, gitea, ollama, workspace, claude) which makes them fairly distinct. However, the system_* and docker_* tools have some overlap in purpose (e.g., system_status vs docker_stats both report resource usage), which could cause minor confusion for an agent.

    Naming Consistency4/5

    All tool names use a consistent pattern of domain_prefix_action (e.g., docker_list, gitea_issues). This makes the set predictable. Minor inconsistency: the workspace tools use git as part of workspace_git rather than git_*, and claude tools are not prefixed uniformly (e.g., claude_ask vs claude_status).

    Tool Count3/5

    With 34 tools, the server covers six domains, but this is on the heavy side for a single server. The claude and ollama domains add 5-6 tools each which feels excessive given that many tasks could be combined (e.g., claude_ask, claude_task, claude_review, claude_explain all serve similar purposes with vague boundaries).

    Completeness3/5

    Each domain has reasonable coverage: system has monitoring, docker has basic lifecycle, gitea has listing and issue creation, ollama has model management. Notable gaps: gitea lacks repo creation/update/deletion and commit reading; workspace lacks file deletion or listing by type; no tool for restarting services or managing users.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources