L
Lmeng486/nano-mcp-termux
更新 2026-10-26
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 0 ★ · Lmeng486/nano-mcp-termux · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
Lmeng486/nano-mcp-termux;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# nano-mcp-termux
以下摘录自该仓库的 README(片段)
> 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
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/lmeng486-nano-mcp-termux/)
- 来源
- awesome · https://github.com/Lmeng486/nano-mcp-termux
- 按领域浏览
- MCP 服务
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。