Documentation
AI assistants and MCP
Breadstick's MCP server lets an AI assistant you choose run commands, use files and see and type into Linux windows, with a key you control (Pro).
Breadstick has a built-in MCP server. MCP, the Model Context Protocol, is how AI assistants and coding agents such as Claude Code connect to tools. With the server on, an assistant you set up can run commands in your Linux system, read and write its files, open Linux apps, and see and type into their windows.
The MCP server is part of Breadstick Pro. It is off until you turn it on.
Turning it on
Settings > Advanced > MCP server. Once it is on, the page shows:
- the address on this device,
http://127.0.0.1:8765/mcpunless you change the Port - the Key, made for this device. Every request has to carry it, as
Authorization: Bearerfollowed by the key. New key makes another one, and the old one stops working at once. Use your own key sets one you choose instead. - Tool calls, a list of every call an assistant made
- how to connect an assistant, inside Linux or outside it
While an assistant is connected, a notification says so.
An assistant inside Linux
An assistant that runs in the Terminal, such as Claude Code, already has a shell. Breadstick gives it
the rest through bsl-mcp, which comes with Breadstick's Linux packages and finds the address and
key by itself:
claude mcp add breadstick bsl-mcp
Other assistants take the same command, bsl-mcp, as a stdio MCP server in their own settings. A
new key, or a server you turned off and on again, needs nothing changed on their side.
An assistant outside Linux
An assistant app on the same device connects to the address on the page with the key. To reach the server from another computer, turn on Allow on the local network: the page then shows the address on your network.
Use that only on a network you trust, and with your own key. Anyone on that network who has the key can run commands in Linux, and the connection is plain HTTP, not encrypted.
What an assistant can do
| Tool | What it does |
|---|---|
run_command |
Runs a shell command in Linux as your Linux user. Root goes through sudo, as for you |
read_file, write_file |
Read and write files in Linux |
list_apps, launch_app |
List the Linux apps in the Apps drawer and open one in its own window |
list_windows, screenshot_window |
List the open Linux windows in Floating mode and take a picture of one |
click, type_text, press_key |
Click in a window, type text and press keys or shortcuts |
clipboard_get, clipboard_set |
Read and set the clipboard, shared with Android |
notify |
Show a notification on your device |
open_on_android |
Open a web or mail link on Android |
list_documentation, read_documentation, search_documentation |
List, read and search these pages, as they are in the app |
Nothing reaches Android beyond those tools. There is no shell on Android, and files outside Linux are reachable only where Linux can already reach them, such as the Android folders you shared with it. Window tools work in Floating mode, where each Linux window is its own Android window.
Before you turn it on
An assistant with these tools can do anything your Linux user can, including deleting files and running programs. Connect only assistants you trust, read the Tool calls list now and then, and turn the server off when you are not using it. Making a new key cuts off every assistant that had the old one.