bash MCP server
Commit 21 Okt 2026Memungkinkan asisten AI untuk mengeksekusi perintah bash pada mesin lokal melalui konektor WebSocket yang aman.
Juga dikenal sebagai assistant-core/mcp-bash
- Stars
- 0
- Tools
- 3
- Unduhan, 30 hari
- —
- Versi terbaru
- —
- Commit terakhir
- 21 Okt 2026
- Lisensi
- MIT
Apa itu bash MCP?
Memungkinkan asisten AI untuk mengeksekusi perintah bash pada mesin lokal melalui konektor WebSocket yang aman. Server ini menyediakan 3 tool, seperti command, timeout_seconds, restart.
Ringkasan dibuat dari README proyek
Tentang bash MCP server
Mengeksekusi perintah terminal secara langsung dari asisten AI adalah fungsi utama yang ditawarkan mcp-bash bagi developer yang bekerja dengan Assistant Core. Server ini bertindak sebagai konektor lokal yang melakukan dial-out via WebSocket untuk menghubungkan mesin Anda ke asisten tanpa memerlukan URL publik atau membuka port. Server ini menyediakan satu tool bash yang memungkinkan model untuk menjalankan perintah, mengelola direktori, serta menerima output seperti stdout dan stderr.
Untuk melakukan setup, Anda menjalankan konektor secara lokal menggunakan token dan URL spesifik yang diberikan oleh admin Assistant Core. Anda dapat menyesuaikan nama tool dan membatasi permukaan mana, seperti aplikasi mobile atau web, yang dapat mengakses fungsionalitas bash. Karena tool ini dapat memodifikasi sistem Anda, ia dirancang untuk digunakan dengan asisten yang terpercaya dan sebaiknya dijalankan di bawah akun dengan hak akses rendah atau di dalam rootless container.
Keamanan dikelola melalui sistem persetujuan di mana Anda dapat mengizinkan (allow), menanyakan (ask), atau memblokir (block) pola perintah tertentu. Server ini juga menyimpan audit log dalam format jsonl untuk melacak setiap perintah yang dieksekusi, termasuk exit code dan durasinya.
Apa yang bisa Anda lakukan dengannya
- 1Otomatisasi tugas terminal yang berulangDeveloper dapat menginstruksikan AI untuk menjalankan git status atau perintah rutin lainnya tanpa perlu mengetik secara manual.
- 2Mengelola banyak mesin remoteAnda dapat menghubungkan beberapa komputer berbeda ke satu asisten yang sama dengan memberikan nama tool yang unik pada setiap konektor.
- 3Mengeksekusi perintah dengan environment variables tertentuAnda dapat mengirimkan kredensial sensitif seperti token GitHub ke tool bash hanya saat tugas tertentu membutuhkannya.
- 4Menjaga koneksi yang berjalan lamaGunakan tmux untuk memastikan konektor bash tetap aktif bahkan setelah Anda memutuskan sesi SSH.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Tool bash MCP 3
Terdeteksi dari READMEcommandtimeout_secondsrestart
| command | — | |
| timeout_seconds | — | |
| restart | — |
Konfigurasi
BASH_TOOL_NAMELOCAL_CONNECTOR_TOKENLOCAL_CONNECTOR_URL
| Nama | Deskripsi | Tipe |
|---|---|---|
| BASH_TOOL_NAME | — | |
| LOCAL_CONNECTOR_TOKEN | — | |
| LOCAL_CONNECTOR_URL | — |
Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Belum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkauassistant-core/mcp-bash is public and reachablegithub.com/assistant-core/mcp-bash ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-10-21github.com/assistant-core/mcp-bash ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model3 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelNo tool named like delete, drop or execLolos
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di GitHubmcp-bash
A minimal MCP server that lets an AI assistant run bash commands on your machine, connected as an Assistant Core local connector. The connector dials out over WebSocket, so the machine needs no public URL or open port.
⚠️ Anyone who can chat with the connected assistant can run commands as your user. Use it only with assistants you trust, run it under a low-privilege account, and stop it when you are done.
Quick start
python -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
# Assistant Core admin → MCP → Local connector → Add connector (token shown once)
export LOCAL_CONNECTOR_URL="wss://api.assistantcore.com/local-connector/ws"
export LOCAL_CONNECTOR_TOKEN="lc_..."
python connector.py
Then click Refresh tools in the admin: the assistant gets one tool, bash. Assistant Core offers a connector's tools only as the owner last refreshed them, so refresh again after changing BASH_TOOL_NAME, BASH_SURFACES or the server.
You can also put both settings in a .env file (see .env.example). To connect a different stdio MCP server, pass its script: python connector.py my_server.py.
Where the tool is offered
On Assistant Core the tool is offered only in the web and mobile apps (BASH_SURFACES=app), never to website widget visitors, messaging apps, voice devices or the public API, where anyone the assistant talks to could run commands. To widen it, list the surfaces: BASH_SURFACES=app,api. The admin can narrow this further, not widen it.
When it asks first
Assistant Core asks before every command unless a rule says otherwise, because the tool can change anything on the machine. The tool tells Assistant Core which argument holds the command line, so rules can name commands instead of the whole tool:
- On an approval card, tick Don't ask again (for commands starting with
git status) to rungit statuswithout asking next time, in chat and in scheduled tasks. Manage these in Settings → Approvals. - The assistant's owner sets rules for everyone in the admin (Approvals): Allow
git status, Ask fordocker, Blockrm. Block wins over Ask, Ask over Allow.
A command line runs without asking only when every command in it is allowed: git status && rm -rf x still asks. Lines with $(…), backticks, redirections or variables, and commands that run other commands (sudo, bash -c, xargs, python…), are never allowed by a command rule.
After updating this server, refresh tools in the admin once so Assistant Core sees the new definition.
Several machines or several assistants
One assistant, several machines. Add a connector per machine in the admin, each with its own token, and give each machine its own tool name so the model can tell them apart:
# on web01, with web01's token
BASH_TOOL_NAME=web01_bash python connector.py
# on db01, with db01's token
BASH_TOOL_NAME=db01_bash python connector.py
Then refresh tools in the admin. A tool name belongs to the connector that offered it first: a second machine offering the same name is refused, and its log says so. Each token connects one machine at a time, and deleting or regenerating one disconnects only that machine.
One machine, several assistants. A connector token belongs to one assistant, so run one connector per assistant, each with its own token and audit log:
LOCAL_CONNECTOR_TOKEN=lc_AAA BASH_AUDIT_LOG=~/audit-a.jsonl python connector.py
LOCAL_CONNECTOR_TOKEN=lc_BBB BASH_AUDIT_LOG=~/audit-b.jsonl python connector.py
Everyone who can chat with any of those assistants can run commands on the machine.
Limit what commands can reach
The server only starts commands; it does not confine them. For anything beyond a personal machine:
- Run the connector as a dedicated user without
sudo, owning only the directories the assistant should touch. - Better, run it in a rootless container with a read-only root filesystem and one writable volume, and restrict its outbound network if you can: commands can send anything they read to the internet.
- Pass secrets with
BASH_PASS_ENVonly when a task needs them, and reviewaudit.jsonl.
Keep it running on a server
To keep the connector running after you close SSH, start it inside tmux:
tmux new -s connector
cd ~/mcp-bash && source .venv/bin/activate && python connector.py
# Ctrl+B then D to detach; the connector keeps running
tmux attach -t connector # back to the logs
tmux kill-session -t connector # stop it
tmux survives SSH disconnects, but not a server reboot, and nothing restarts the connector if it exits.
The bash tool
| Parameter | Description |
|---|---|
command |
Bash command to run |
timeout_seconds |
1–120, default 30 |
restart |
Start from BASH_WORKDIR instead of where the last command ended |
Returns stdout, stderr, exit_code, timed_out, truncated and cwd (where the command ended).
- The first command starts in
BASH_WORKDIR(default: your home directory); each later one starts where the previous one ended, like a terminal. Environment variables, aliases and functions do not carry over: every call is a new shell. A command that times out keeps the directory it started in. This is a starting point, not a sandbox. - Commands see only a minimal environment (
PATH,HOME,USER,SHELL, locale,TERM,TMPDIR,TZ), so secrets in your shell, including the connector token, never reach the assistant. Pass extra variables explicitly withBASH_PASS_ENV=GITHUB_TOKEN,AWS_PROFILE; anything you pass, the assistant can read. - stdin is closed, so commands that prompt for input fail instead of hanging.
- On timeout the whole process group is killed. A process that starts its own session (
setsid) can outlive it; there is no sandbox to stop that. - Background jobs keep running after the command returns; redirect their output (
cmd > log 2>&1 &), since the result is returned as soon as bash exits. - stdout and stderr are each truncated to 20,000 characters, keeping the first 8,000 and the last 12,000, and memory stays bounded however much a command prints.
- At most 2 commands run at once; extra calls return an error.
- Every command is appended to
audit.jsonlnext tobash_server.py(orBASH_AUDIT_LOG): time, command, starting directory, exit code and duration, not the output. The file is readable only by you. - Requires bash (macOS, Linux, or WSL on Windows).
Reconnection
connector.py reconnects with exponential backoff (1 s up to 10 min), and starts over after a session that stayed up for a minute. If the connector token is regenerated or deleted in the admin, the log says so; restart with the new token. If the relay refuses the connection because the token is already in use or another machine offers the same tool name, the log names the conflict.
Tests
pip install pytest && pytest -q
Pertanyaan tentang bash MCP
Tool apa yang disediakan bash MCP?
Server ini menyediakan 3 tool, termasuk command, timeout_seconds, restart.
Bagaimana cara menjalankan perintah bash melalui server ini?
Server menyediakan tool bash yang menerima string perintah, opsi timeout, dan flag restart untuk menentukan working directory.
Bisakah saya membatasi perintah apa saja yang boleh dijalankan oleh asisten?
Ya, admin Assistant Core dapat mengatur aturan untuk Allow, Ask, atau Block perintah tertentu, di mana aturan Block akan diprioritaskan.
Bagaimana konektor menangani konektivitas jaringan?
Konektor melakukan dial-out melalui WebSocket, yang berarti mesin Anda tidak memerlukan URL publik atau port yang terbuka, dan menggunakan exponential backoff untuk koneksi ulang.