get_ssh_session_listLABSCO SUMMARY
Your terminal, not a hidden one.
Commands run in the tab in front of you, with your environment, your SSH session and your shell history — so the model is working in the same place you are rather than in a sandbox you then have to reconcile. Pair programming mode ships on by default, which puts a confirmation dialog between the model and execution; there is a health endpoint and a plain HTTP test path if you want to poke at a tool before connecting a client.
What it is
A plugin for the Tabby terminal that exposes your live terminal sessions over MCP. Tabby stays the terminal you use; an MCP-capable client connects to it over an SSE endpoint and works in the same tabs you can see.
What you get
- The available Tabby terminal sessions, local and SSH-backed, listed for the client —
get_ssh_session_list - A shell command run in a chosen tab, with exit-code parsing from a marker protocol —
exec_command - Terminal buffer content read back over a line range, visible screen or history —
get_terminal_buffer - Long command output retrieved in full or by page, by
outputId—get_command_output - Pair programming mode: a confirmation dialog before execution, optional terminal auto-focus, command rejection with feedback, and a result dialog with history
Requirements
Tabby Terminal installed and running, with the plugin loaded and at least one terminal tab open — the client cannot connect before that. An MCP client with SSE support such as Claude Code, Cursor, Windsurf or Codex, pointed at http://localhost:3001/sse. Install from the Tabby Plugin Store, or build locally, which needs Docker and follows a macOS install-script path. The npm package is tabby-mcp at 1.0.3. The default configuration starts the server on boot on port 3001 with pair programming mode and its confirmation dialog switched on, all editable under Settings → Plugins → MCP.
Setup effort
Follow the published steps — Open Tabby
USE CASES
01
Running a command on a server you are already logged into
Pick the existing SSH-backed tab and execute there, reusing the session instead of authenticating again.
02
Getting help with what just went wrong
Read back the terminal buffer around the failure so the model sees the actual error text rather than your paraphrase.
03
Working through output too long for one response
Fetch the stored output by its id and page through it in slices instead of truncating.
04
Keeping a hand on the wheel
Leave pair programming mode on so every command waits for your confirmation, with the option to reject and explain why.
4 tools
Listed in project docs. Your client may show a different list.
exec_commandget_terminal_bufferget_command_outputBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- Tabby Terminal installed and running
- An MCP client with SSE support
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
Open Tabby
Go to Settings → Plugins
Install Tabby MCP → Restart Tabby
Open Settings → Plugins → MCP and confirm the server configuration (it serves http://localhost:3001/sse), keep a terminal tab open, then add that SSE endpoint to your client
MCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"tabby-mcp": {
"type": "sse",
"url": "http://localhost:3001/sse"
}
}
}Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport sse tabby-mcp http://localhost:3001/sse
