Skip to main content
Glama
Sign In
termux-mcp-bridge

termux-mcp-bridge

by belacorc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to termux-mcp-bridge

No user-submitted related servers found.

    Related Servers

    • adbmcp

      wu737
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to operate adb-connected devices through natural language by exposing shell execution, file management, screenshots, notifications, and system information tools over a local MCP endpoint. It supports wireless device access from a phone-hosted Termux environment with automatic reconnection and dangerous-command confirmation.
      MIT

    • phone-mcp-server

      hazure
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to securely interact with an Android device running Termux, executing shell commands with configurable timeouts, smart output truncation, and MCP Streamable HTTP transport for multi-session clients.
      MIT

    • termux-mcp

      leemwood
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients running on the same Android device to drive Termux over localhost, covering command execution, persistent tmux interactive terminals, background tasks, file management, and Termux:API features like clipboard, notifications, and TTS.
      33
      8 npm
      3
      MIT

    • termux-mcp

      YSCodex
      A
      license
      Not graded
      quality
      C
      maintenance
      Turns an Android phone running Termux into a remotely drivable machine, letting an AI agent run shell commands, manage background jobs and tmux sessions, read and write files, install packages, and use Android device features such as battery status, screenshots, notifications, SMS and sensors. It can be reached either over stdio on the same device or over Streamable HTTP with bearer tokens and token scopes from anywhere on the local network, with a confirmation gate on destructive actions, a jailed file API and an audit log.
      8 npm
      1
      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.4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each dedicated tool targets a distinct phone capability (apps, URL, notification, status, location, clipboard, TTS) and descriptions make the intended use clear. The main overlap is `shell`, which can perform almost every other tool's job (e.g. `am start`, `termux-notification`, `termux-clipboard-get`), and `open_url` vs `open_app` can blur when a URL deep-links into an app, but an agent can still choose reliably.

    Naming Consistency3/5

    The set mixes bare nouns (`shell`, `location`, `clipboard`), bare verbs (`notify`, `speak`), and verb_noun pairs (`list_apps`, `open_app`, `open_url`), plus a noun_noun form (`phone_status`). All names use snake_case and are readable, so it is inconsistent but not chaotic.

    Tool Count5/5

    Nine tools for a phone-control bridge is well-scoped: one general shell plus a small set of convenience wrappers for common device actions. Nothing feels redundant beyond the intentional shell escape hatch, and nothing is missing at the count level.

    Completeness4/5

    The surface covers the core remote-control lifecycle: command execution, app discovery/launch, URL handling, notifications, device status, location, clipboard, and TTS. Notable gaps include SMS/contacts, camera/media, file push/pull, and input injection, though most of these can be reached through `shell` (am/pm/termux-api), so agents are not hard-blocked.

    Resources