vscode-terminal-mcp

MCP server that executes commands in visible VSCode terminal tabs with full output capture. Unlike inline execution, every command runs in a real terminal you can see, scroll, and interact with.

Key Features

• Visible Terminals: Commands run in real VSCode terminal tabs, not hidden processes. You see everything in real time.
• Session Reuse: The run tool automatically reuses idle sessions, creating new terminals only when needed.
• Long-Running Support: Fire-and-forget execution with waitForCompletion: false, then poll output incrementally with read.
• Subagent Isolation: Tag sessions with agentId to keep parallel agent workloads separated.

Requirements

• VS Code 1.93+ (for Shell Integration API)
• Node.js 20+

Getting Started

Claude Code

claude mcp add BashTerm -- npx vscode-terminal-mcp@latest

VS Code / Copilot

Add to your .vscode/mcp.json:

{
  "servers": {
    "BashTerm": {
      "type": "stdio",
      "command": "npx",
      "args": ["vscode-terminal-mcp@latest"]
    }
  }
}

{
  "mcpServers": {
    "BashTerm": {
      "command": "npx",
      "args": ["-y", "vscode-terminal-mcp@latest"]
    }
  }
}

{
  "mcpServers": {
    "BashTerm": {
      "command": "npx",
      "args": ["-y", "vscode-terminal-mcp@latest"]
    }
  }
}

Your First Prompt

After installation, try asking:

Run ls -la in the terminal

You should see a new terminal tab open in VSCode with the command output.

Tools

Quick Execution

Session Management

Usage Patterns

Simple Command

The run tool handles everything — creates a terminal if needed, executes, and returns clean output:

> Run npm test

$ npm test
PASS src/utils.test.ts (3 tests)
PASS src/index.test.ts (5 tests)

[exit: 0 | 1243ms | session-abc123]

Long-Running Process

For builds, deployments, or any command that takes a while:

> Start `npm run build` without waiting, then check progress

The agent will:

1. Call run with waitForCompletion: false — returns immediately
2. Call read with offset: -10 to check the last 10 lines
3. Repeat until the process completes

Interactive Commands

For commands that need user input:

> Run npm init and answer the prompts

The agent will:

1. Call run with npm init
2. Call read to see the prompt
3. Call input to send the answer

Parallel Agents

Subagents can work in isolated terminals using agentId:

> Have one agent run tests while another runs the linter

Each subagent gets its own terminal tagged with its agentId, preventing output from mixing.

Configuration

The extension reads configuration from VSCode settings under terminalMcp.*:

Recommended: Set as Preferred Tool

LLM agents like Claude Code have a built-in Bash tool that executes commands inline within the chat. The output is embedded in the conversation and hard to read, especially for commands with verbose output. We recommend telling the agent to prefer this MCP over its built-in Bash tool.

Add the following to your project's CLAUDE.md (or equivalent instructions file):

## Terminal Execution

Prefer the BashTerm MCP tools (`run`, `exec`, `read`, etc.) over the built-in Bash tool for executing commands.
BashTerm runs commands in visible VSCode terminal tabs where the user can see output in real time.
Only fall back to the built-in Bash tool for simple, non-interactive operations like reading environment variables.

For commands that may take longer than 30 seconds or produce large amounts of output (builds, test suites,
deployments, installs), use the pull mode pattern:
1. Call `run` with `waitForCompletion: false` to launch the command without blocking.
2. Call `read` with `offset: -10` to check the last 10 lines of output.
3. Repeat step 2 until you see the command has finished (look for exit messages, prompts, or "Done").
4. Report the final result to the user.

This prevents conversation timeouts and lets the user watch progress in the terminal in real time.

Why this matters:

Development: Updating the Extension

VSCode aggressively caches extensions in memory. When developing locally, code --install-extension and even "Developer: Reload Window" may not reload your changes. Use this workflow:

Quick update (no restart needed)

After modifying source files, build and copy directly into the installed extension directory:

cd /path/to/vscode-terminal-mcp
npm run build
cp dist/extension.js ~/.vscode/extensions/sirlordt.vscode-terminal-mcp-<version>/dist/extension.js

Then run "Developer: Reload Window" (Ctrl+Shift+P).

Full reinstall (when quick update doesn't work)

If VSCode still uses old code:

# 1. Uninstall and remove all copies
code --uninstall-extension sirlordt.vscode-terminal-mcp
rm -rf ~/.vscode/extensions/sirlordt.vscode-terminal-mcp-*

# 2. Check for ghost entries with old publisher names
# Look in ~/.vscode/extensions/extensions.json for stale entries
# Remove any entries with old publisher IDs (e.g., "terminal-mcp.vscode-terminal-mcp")

# 3. Close VSCode completely (not just reload)

# 4. Rebuild and install
npm run build
npx vsce package --allow-missing-repository
code --install-extension vscode-terminal-mcp-<version>.vsix --force

# 5. Open VSCode

Verify the correct version is loaded

# Check which extension directories exist
ls ~/.vscode/extensions/ | grep terminal

# Verify your changes are in the installed extension
grep "YOUR_UNIQUE_STRING" ~/.vscode/extensions/sirlordt.vscode-terminal-mcp-*/dist/extension.js

# Compare checksums
md5sum dist/extension.js ~/.vscode/extensions/sirlordt.vscode-terminal-mcp-*/dist/extension.js

How It Works

1. The VSCode extension activates and starts an IPC server on a Unix socket
2. The MCP entry point (mcp-entry.js) is spawned by the MCP client and bridges JSON-RPC stdio with the IPC socket
3. Commands execute in real VSCode terminals using the Shell Integration API for reliable output capture and exit code detection
4. Output is stored in circular buffers with pagination support for efficient reading

License

MIT