Get the FREE Ultimate OpenClaw Setup Guide →

wezterm

About A Model Context Protocol server that executes commands in the current WezTerm session

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio hiraishikentaro-wezterm-mcp npx -y wezterm-mcp

How to use

WezTerm MCP Server lets you control WezTerm from Claude Desktop and other MCP clients. Through this server, you can issue commands to WezTerm to manage terminals, tabs, panes, and layouts from your MCP-enabled interface, enabling scripted and remote control of your WezTerm sessions. This enables workflow automation, macro-like actions, and orchestration of terminal tasks across tools that support MCP.

To use it, configure the MCP client to point at the wezterm-mcp server (as shown in the installation example). Once running, send MCP commands to open new tabs, spawn panes, send text to a pane, or adjust layout depending on the capabilities exposed by the server. The integration is designed to work smoothly with Claude Desktop, but it should be compatible with other MCP clients as well, enabling cross-application automation of your terminal environment.

How to install

Prerequisites:

  • Node.js and npm or npx available on your system.
  • Access to a terminal or shell.

Installation steps:

  1. Verify Node.js and npm are installed:

    • node -v
    • npm -v
  2. Install and run the MCP server via npx (as recommended in the README):

    • npx -y wezterm-mcp
  3. Add the MCP server configuration to your client (Claude Desktop or other MCP client) as shown: { "mcpServers": { "wezterm-mcp": { "command": "npx", "args": ["-y", "wezterm-mcp"] } } }

  4. Start or load your MCP configuration in your client and connect to the wezterm-mcp server. The server will expose WezTerm control capabilities to the client.

Additional notes

Notes and tips:

  • The server is invoked via npx with the wezterm-mcp package, so an active internet connection may be required the first time to fetch the package.
  • If you plan to automate frequently, consider pinning the package version or using a local cache to avoid network delays.
  • Ensure that WezTerm is installed on the host where the MCP server is controlling it, as the MCP server acts as a bridge to WezTerm functionality.
  • If you encounter compatibility issues with specific MCP clients, verify that the client is issuing supported commands exposed by the wezterm-mcp server.

Related MCP Servers

Sponsor this space

Reach thousands of developers