Skip to main content
Glama
nano-mcp-termux

nano-mcp-termux

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NANO_NO_WATCHDOGNoSet to 1 to disable the parent-process watchdog thread. Unset by default.
NANO_IDLE_TIMEOUTNoSeconds of inactivity before the server exits on its own. Default is 0 (off).0

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
device_statusA

Read-only snapshot of the host hardware and OS: battery level, storage usage, CPU architecture and memory. Use it when the answer depends on the physical device: free space before a download, battery before a long job, arch before picking a binary. Not for process or server state: use server_health for pid/uptime/counters of this MCP server, resolve_path to validate one path, and path_adapter for the runtime's path environment. Never raises: a field that cannot be read is reported with source unavailable. Returns {battery, storage, arch, memory}.

server_healthA

Read-only self-diagnostics for this MCP server process: pid/ppid, runtime class, uptime, request and tool-call counters, tracked live child processes, RSS, and the Android Phantom Process Killer risk assessment. Use it to verify the server is alive, to debug client-side disconnects, or to check whether orphaned children are accumulating on Android. Not for the device itself: use device_status for battery, storage, arch and memory. Returns {server, children, memory, phantom_process}.

resolve_pathA

Resolve and validate one filesystem path in the runtime this server runs in: expands ~/$HOME/$PREFIX/$TMPDIR, follows symlinks, reports the mount backing the path, and lists every Android-equivalent spelling (/sdcard <-> /storage/emulated/0 <-> $HOME/storage/shared). Equivalent inputs: /sdcard/Download/x.txt, $HOME/storage/shared/Download/x.txt, ~/storage/shared/Download/x.txt, and relative docs/report.md (against cwd). Expansion: ~ and $HOME become the server's HOME; $PREFIX is the install prefix (e.g. /data/data/com.termux/files/usr); $TMPDIR is the server's own temp dir, never the client's. Useful when a path has to be handed to a shell command or another tool; not needed for paths already known-good on plain Linux. Sibling boundary: path_adapter reports the environment map itself (env class, HOME/PREFIX/TMPDIR, mount roots) and takes no arguments; resolve_path reports one concrete path. Use path_adapter for the environment, resolve_path for a candidate path. Returns {input, expanded, resolved, env, exists, is_dir, is_file, is_symlink, readable, writable, executable, mount, alternatives, warnings}.

path_adapterA

Report the runtime's path environment so you can translate host paths correctly: detected env class (termux/proot/android/linux), HOME/PREFIX/TMPDIR, each Android shared-storage root with its real mount, all noexec mounts that block in-place script execution, and runtime-specific notes. Takes no arguments. Sibling boundary: this answers the environment question (env class, HOME/PREFIX/TMPDIR, mount roots); resolve_path answers the per-path question (expansion, mount, alternatives for one path). Use path_adapter when the environment itself is unknown, resolve_path to validate a single candidate path. Returns {env, home, prefix, tmpdir, python, platform, android_roots, noexec_mounts, notes}.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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