Skip to main content
Glama
ServerkitOfficial

serverkit-mcp

Related Servers

Alternatives to serverkit-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agent clients to safely connect to tools and execution resources through MCP with authorization, approvals, audit, chat-context isolation, SSH/Docker access, and long-running command session tracking.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to connect to remote MCP servers once, access their tools through a compact MCP endpoint, pair a CLI inside sandboxes, and create watches that turn command or tool output into pollable structured events.
      2
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to discover and interact with iOS apps through a local MCP gateway, converting remote Streamable HTTP MCP endpoints into stdio tools. Provides dynamic device discovery, tool schema introspection, and deterministic tool calling for app analysis.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Connects local tools (browser, shell) to a remote MCP server via reverse-MCP, enabling the server agent to control your local browser and execute shell commands.
      840 npm
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Connects any MCP host to the Haven Agent Gateway, enabling session creation, agent discovery, collaboration, handoff, and work operations through MCP tools over stdio or Streamable HTTP.
      13
      557 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that enables running structured commands and fleet operations on SSH hosts, supporting secure file transfer, persistent sessions, and bastion-based discovery.
      -

    TDQS

    A3.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool maps to a distinct stage in a clear lifecycle: discovery, connection, session, and command execution. The only near-overlap is run_command vs run_command_sudo, but the sudo distinction is spelled out explicitly in both descriptions. An agent can easily pick the right tool at each step.

    Naming Consistency4/5

    Almost everything follows a consistent snake_case verb_noun pattern (discover_servers, start_session, end_session, run_command, run_command_sudo). The only minor deviations are the bare connect/disconnect pair, which are still predictable and readable, plus the _sudo suffix variant.

    Tool Count5/5

    Seven tools is well-scoped for a remote-command bridge: discovery, connection management, session management, and command execution. Every tool earns its place with no redundant or filler entries.

    Completeness4/5

    The connection-to-command lifecycle is fully covered (discover, connect, start/end session, run, run with sudo). Minor gaps exist around introspection such as checking connection/session status or transferring files, but core workflows have no dead ends.