L
Lmeng486/nano-mcp-termux
updated 2026-10-26
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · Lmeng486/nano-mcp-termux · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
Lmeng486/nano-mcp-termux;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# nano-mcp-termux
Excerpted from the repository README (abridged)
> Zero-dependency, single-file MCP server for AI agents, natively running on Termux (Android), Raspberry Pi, and Linux.
## 🚀 Quick Start
### Local (Termux / Linux)
bash
cd /path/to/nano-mcp-termux
python3 nano_mcp_termux.py
### Docker
bash
docker build -t nano-mcp-termux .
docker run -i --rm nano-mcp-termux
### Health check (one-shot, no MCP handshake)
bash
python3 nano_mcp_termux.py --health
## 🔌 Connect to your MCP client
This server does not run standalone — it's a sidecar that your AI client connects to via the MCP protocol.
Below are the three most common ways to mount it.
### Option 1 — Zero‑install (uvx), best for desktop AI clients
bash
uvx nano-mcp-termux
Then add this JSON to your AI client's mcpServers config (see client‑specific notes below):
json
"mcpServers": {
"nano-mcp-termux": {
"command": "uvx",
"args": ["nano-mcp-termux"]
### Option 2 — Already pip installed, or you prefer a direct Python launch
bash
pip install nano-mcp-termux
Config snippet for your AI client:
json
"mcpServers": {
"nano-mcp-termux": {
"command": "nano-mcp-termux"
### Option 3 — Run the single file directly (e.g. inside Termux on Android)
bash
# Clone or download the repo, then:
cd /path/to/nano-mcp-termux
python3 nano_mcp_termux.py
Config snippet for your AI client:
json
"mcpServers": {
"nano-mcp-termux": {
"command": "python3",
"args": ["/full/path/to/nano_mcp_termux.py"]
### How to use these snippets: client‑specific config files
| AI client | Config file location (examples) | Note |
| Claude Desktop | macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json | ∆ mcpServers key at top level |
| Cursor | ~/.cursor/mcp.json | ∆ mcpServers key at top level |
| Cline | $HOME/.cliner/mcp.json (or inside project folder as cline_mcp_settings.json) | ∆ mcpServers key at top level |
| Cherry Studio | GUI → MCP section (typically auto‑creates ~/.cherrystudio/mcp/.json) | JSON schema as above |
| Operit | ~/.operit/mcp_config.json (or per‑workspace config in the workspace folder) | ∆ mcpServers key at top level |
Tip: after editing the config file, restart your AI client so the new server is detected. If the client supports hot‑reload, you may not need a restart.
### Troubleshooting
| Symptom | Likely cause | Fix |
| Client shows "server not found" | command path is wrong or not in PATH | Use absolute path (/usr/local/bin/nano-mcp-termux for pip installs, $HOME/.local/bin/nano-mcp-termux for pip --user) |
| Error: spawn uvx ENOENT | uvx not in PATH (not installed) | Use a custom shell like "shell": "uw uvx" or the direct Python launch (Option 2) |
| "Connection lost" / process dies immediately | No stdin from client | This server is stdio‑bound; don't run it directly like nano-mcp-termux — always launch it through your client's MCP config |
## 🛠️ Features
✅ Zero-dependency: No external packages required
✅ Single-file: All logic in one Python script
✅ Cross-platform: Works in Termux (Android), on Raspberry Pi, Linux, and inside Docker
✅ Container-ready: Dockerfile at repo root for Glama introspection
✅ Standard stdio framing: Newline-delimited JSON-RPC (official MCP transport)
✅ Version negotiation: Echoes client protocolVersion (2024-11-05 / 2025-06-18 / 2025-11-25), falls back to highest supported
## 🚀 Quick Start
### Local (Termux / Linux)
bash
cd /path/to/nano-mcp-termux
python3 nano_mcp_termux.py
### Docker
bash
docker build -t nano-mcp-termux .
docker run -i --rm nano-mcp-termux
### Health check (one-shot, no MCP handshake)
bash
python3 nano_mcp_termux.py --health
## 🔌 Connect to your MCP client
This server does not run standalone — it's a sidecar that your AI client connects to via the MCP protocol.
Below are the three most common ways to mount it.
### Option 1 — Zero‑install (uvx), best for desktop AI clients
bash
uvx nano-mcp-termux
Then add this JSON to your AI client's mcpServers config (see client‑specific notes below):
json
"mcpServers": {
"nano-mcp-termux": {
"command": "uvx",
"args": ["nano-mcp-termux"]
### Option 2 — Already pip installed, or you prefer a direct Python launch
bash
pip install nano-mcp-termux
Config snippet for your AI client:
json
"mcpServers": {
"nano-mcp-termux": {
"command": "nano-mcp-termux"
### Option 3 — Run the single file directly (e.g. inside Termux on Android)
bash
# Clone or download the repo, then:
cd /path/to/nano-mcp-termux
python3 nano_mcp_termux.py
Config snippet for your AI client:
json
"mcpServers": {
"nano-mcp-termux": {
"command": "python3",
"args": ["/full/path/to/nano_mcp_termux.py"]
### How to use these snippets: client‑specific config files
| AI client | Config file location (examples) | Note |
| Claude Desktop | macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json | ∆ mcpServers key at top level |
| Cursor | ~/.cursor/mcp.json | ∆ mcpServers key at top level |
| Cline | $HOME/.cliner/mcp.json (or inside project folder as cline_mcp_settings.json) | ∆ mcpServers key at top level |
| Cherry Studio | GUI → MCP section (typically auto‑creates ~/.cherrystudio/mcp/.json) | JSON schema as above |
| Operit | ~/.operit/mcp_config.json (or per‑workspace config in the workspace folder) | ∆ mcpServers key at top level |
Tip: after editing the config file, restart your AI client so the new server is detected. If the client supports hot‑reload, you may not need a restart.
### Troubleshooting
| Symptom | Likely cause | Fix |
| Client shows "server not found" | command path is wrong or not in PATH | Use absolute path (/usr/local/bin/nano-mcp-termux for pip installs, $HOME/.local/bin/nano-mcp-termux for pip --user) |
| Error: spawn uvx ENOENT | uvx not in PATH (not installed) | Use a custom shell like "shell": "uw uvx" or the direct Python launch (Option 2) |
| "Connection lost" / process dies immediately | No stdin from client | This server is stdio‑bound; don't run it directly like nano-mcp-termux — always launch it through your client's MCP config |
## 🛠️ Features
✅ Zero-dependency: No external packages required
✅ Single-file: All logic in one Python script
✅ Cross-platform: Works in Termux (Android), on Raspberry Pi, Linux, and inside Docker
✅ Container-ready: Dockerfile at repo root for Glama introspection
✅ Standard stdio framing: Newline-delimited JSON-RPC (official MCP transport)
✅ Version negotiation: Echoes client protocolVersion (2024-11-05 / 2025-06-18 / 2025-11-25), falls back to highest supported
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/lmeng486-nano-mcp-termux/)
- Source
- awesome · https://github.com/Lmeng486/nano-mcp-termux
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.