Tabby MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Tabby MCP Serverlist my active terminal sessions and show the buffer for the first one"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Tabby MCP Server
A Tabby Terminal plugin that exposes your active terminal sessions through the Model Context Protocol (MCP). It lets MCP-compatible AI clients discover terminal tabs, execute commands, read terminal buffers, and retrieve long command output.
Tabby stays the terminal UI. Your AI client connects to Tabby through MCP.
Highlights
MCP server inside Tabby — exposes an SSE endpoint at
http://localhost:3001/sseTerminal session discovery — list local and SSH-backed Tabby terminal sessions
Command execution — run commands in a selected Tabby terminal tab
Robust output capture — simple marker protocol with exit-code parsing
Terminal buffer access — read visible/history buffer ranges from a tab
Long output pagination — retrieve full command output by
outputIdPair programming mode — optional confirmation dialogs and user feedback
Docker-based build — reproducible local plugin builds for Tabby
Related MCP server: TermPipe MCP
Demo

Table of Contents
Requirements
Tabby Terminal installed and running
Docker, for local builds
macOS for the provided install script path
An MCP-compatible client with SSE support, such as Claude Code, Cursor, Windsurf, Codex, or another SSE-capable MCP client
Installation
Option 1: Tabby Plugin Store
Open Tabby
Go to Settings → Plugins
Install Tabby MCP
Restart Tabby
Open Settings → Plugins → MCP and confirm the server configuration
Option 2: Local Docker Build
git clone https://github.com/thuanpham582002/tabby-mcp-server.git
cd tabby-mcp-server
make build-dist
bash scripts/copy_to_plugin_folder.shThe install script copies the plugin to:
~/Library/Application Support/tabby/plugins/node_modules/tabby-mcpRestart Tabby after installing or updating the plugin.
If your local Tabby installation requires bundled plugin dependencies, build the full package:
make build-dist-with-deps
bash scripts/copy_to_plugin_folder.shQuick Start
Start or restart Tabby
Open at least one terminal tab
Verify the MCP server is running:
curl http://localhost:3001/health
# OKList Tabby terminal sessions:
curl -X POST http://localhost:3001/api/tool/get_ssh_session_list \
-H 'Content-Type: application/json' \
-d '{}'Execute a command in a session:
curl -X POST http://localhost:3001/api/tool/exec_command \
-H 'Content-Type: application/json' \
-d '{"command":"pwd","tabId":"0"}'Connecting MCP Clients
Tabby-MCP provides:
SSE endpoint: http://localhost:3001/sse
Health endpoint: http://localhost:3001/health
HTTP test API: http://localhost:3001/api/tool/<tool-name>The Tabby plugin must be running before clients can connect.
SSE clients
Use this configuration for clients that support SSE MCP servers directly:
{
"mcpServers": {
"tabby-mcp": {
"type": "sse",
"url": "http://localhost:3001/sse"
}
}
}For Cursor-style clients, place it in the MCP config file, for example:
~/.cursor/mcp.jsonClaude Code
If your Claude Code version supports SSE MCP servers:
claude mcp add --transport sse tabby-mcp http://localhost:3001/sseIf your setup uses JSON config, use the SSE clients configuration.
Codex / OpenAI Codex CLI
Use the SSE MCP server configuration supported by your Codex client:
{
"mcpServers": {
"tabby-mcp": {
"type": "sse",
"url": "http://localhost:3001/sse"
}
}
}For TOML-based configs, map the same SSE URL using your client's supported SSE MCP syntax.
Tools
Tool | Description | Parameters |
| List available Tabby terminal sessions | none |
| Execute a shell command in a terminal tab |
|
| Read terminal buffer content |
|
| Retrieve full/paginated command output |
|
Configuration
Default plugin configuration:
{
"mcp": {
"enabled": true,
"startOnBoot": true,
"port": 3001,
"serverUrl": "http://localhost:3001",
"enableDebugLogging": true,
"pairProgrammingMode": {
"enabled": true,
"showConfirmationDialog": true,
"autoFocusTerminal": true
}
}
}Configure these options in Tabby under Settings → Plugins → MCP.
Pair Programming Mode
Pair Programming Mode adds safety prompts when an AI client executes commands:
confirmation before command execution
optional terminal auto-focus
command rejection with feedback
command result dialog and history tracking
Development
Clone and build:
git clone https://github.com/thuanpham582002/tabby-mcp-server.git
cd tabby-mcp-server
make build-distInstall into local Tabby:
bash scripts/copy_to_plugin_folder.shRestart Tabby and verify:
curl http://localhost:3001/healthBuild targets
make build-dist # Build dist only
make build-dist-with-deps # Build dist and copy node_modules
make help # Show available targetsLicense
MIT — see LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Connect AI assistants to your GitHub-hosted Obsidian vault to seamlessly access, search, and analy…
Run, debug, and triage tests from your IDE using natural language, no dashboard switching, no manual data transfers. The TestMu AI (formerly LambdaTest) MCP Server is a single remote server exposing four tool suites: HyperExecute — analyze your project, generate YAML configs and test runner commands, then monitor jobs and sessions. Automation — pull a TestID's details plus command, network, and console logs into one chat for instant root-cause analysis. Includes mobile app upload. SmartUI — explain pixel, layout, DOM, and perceptual changes in a visual regression run, with context-aware React/HTML/CSS fixes. Accessibility — audit any public URL or a local React app against WCAG and get ready-to-apply remediation steps. Connects over https://mcp.lambdatest.com/mcp using OAuth 2.1 — no API keys in your config. One-click install in Cursor; works with Claude, GitHub Copilot, Cline, and any MCP client. Tests execute on the TestMu AI cloud: 3,000+ browsers and 10,000+ real devices.
Related MCP Servers
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables AI assistants to interact with iTerm2 terminals, allowing creation and management of terminal sessions, command execution, and reading terminal output.516 npm14ISC
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with direct terminal access to execute commands, manage files, and run persistent REPL sessions. It features automated installation scripts that educate AI assistants on its capabilities for seamless integration.MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server plugin for the Tabby Terminal that enables AI assistants to execute commands, read terminal buffers, and manage tabs and profiles. It features 18 specialized tools for comprehensive terminal control and session management with built-in security confirmations.287 npm55MIT
- AlicenseAqualityFmaintenanceEnables AI assistants to execute terminal commands on a host machine with configurable, granular permission controls and safety protections. It features multiple security modes, including allowlists and manual approval, to ensure safe command execution within specified directories.6Apache 2.0