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

nano-mcp-termux

by Lmeng486
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nano-mcp-termux

No user-submitted related servers found.

    Related Servers

    • air

      airmcp-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      SDK-free MCP server framework with self-implemented protocol engine (MCP 2026-07-28 + legacy), 19 built-in plugins, OWASP MCP Top 10 security, and zero external dependencies.
      52 npm
      2
      MIT

    • ChatGPT Desktop Commander MCP

      kathirm1323-ai
      F
      license
      Not graded
      quality
      D
      maintenance
      A Python MCP server that allows ChatGPT to execute commands on your local PC via a secure Cloudflare tunnel.
      -

    • MCPServe

      mifunedev
      A
      license
      Not graded
      quality
      D
      maintenance
      A simple MCP Server with shell execution capabilities that can be run locally with Ngrok tunneling or hosted in an Ubuntu 24 Docker container.
      4
      MIT

    • mcp-lite

      srsergi0
      A
      license
      Not graded
      quality
      D
      maintenance
      Ultra-lightweight MCP server for Bun with full protocol compliance. Enables building MCP servers with tools, resources, and prompts using minimal dependencies and heap footprint.
      46,312 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct question: device hardware (device_status), server process state (server_health), one candidate path (resolve_path), and the runtime path environment (path_adapter). Descriptions explicitly state sibling boundaries and even tell the agent which tool to use instead, eliminating misselection.

    Naming Consistency4/5

    All names are snake_case and self-describing, with a clear domain term per tool. The pattern is noun_noun for three tools (device_status, server_health, path_adapter) and verb_noun for one (resolve_path), a minor deviation that is still highly readable.

    Tool Count4/5

    Four tools is on the small side but each covers a distinct, non-overlapping diagnostic concern, so nothing feels padded or redundant. The surface is tightly scoped to introspection rather than trying to be a general shell wrapper.

    Completeness4/5

    The stated domain — read-only device, server, and path introspection — is well covered, including Android-specific concerns like phantom processes and shared-storage aliases. Minor gaps remain (no general process/network/log inspection), but agents can work around these via other tools or shell commands.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources