Skip to main content
Glama
Sign In
raspberry-pi-connect-mcp

raspberry-pi-connect-mcp

by kritzerenkrieg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to raspberry-pi-connect-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-ssh

      seraved
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to run commands on remote SSH-accessible devices via persistent sessions, supporting both POSIX and CLI shells with safety filters.
      -

    • pty-mcp

      brkhrdt
      F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to start and manage pseudo-terminal sessions, run shell commands and interact with REPLs programmatically.
      7
      -

    • mcp-ssh-terminal

      zhdkirill
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to have persistent, fully interactive SSH sessions into remote hosts, behaving like a local terminal.
      15 npm
      2
      MIT

    • SSH MCP Server

      format37
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to securely execute shell commands on local machines through an SSH interface with session management, command execution, and sudo support.
      1
      -

    • fast-mcp-ssh

      klNuno
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to securely execute commands on remote hosts via SSH and SFTP, with persistent shells, file transfers, screenshots, and an audit log.
      5
      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.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a distinct role, but run_command and send_keys both push input to a device shell, and the boundary between them is only clarified by description text rather than by the names alone. The descriptions do a good job of steering usage (non-interactive vs interactive), so misselection is unlikely but not impossible.

    Naming Consistency5/5

    All five tools follow a clean verb_noun pattern: list_devices, run_command, send_keys, read_screen, close_session. No camelCase mixing or vague standalone verbs.

    Tool Count5/5

    Five tools is a tight, well-scoped set for remote shell management, and every tool maps to a necessary step in the workflow (discover, execute, interact, inspect, tear down). Nothing feels padded or missing from a count perspective.

    Completeness4/5

    The interactive session lifecycle is well covered: discover devices, run commands, send keystrokes, read output, close session. Minor gaps exist—there is no explicit open/connect tool or session listing, and no file transfer—but sessions are opened implicitly and agents can work around this.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources