Browser Use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Description from the maker (original English)
MCP server for AI agents to interact with terminal applications. Think Playwright for terminals.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
DISPLAY, RUST_LOGYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"terminal": {
"command": "npx",
"args": [
"-y",
"mcp-server-terminal"
],
"env": {
"DISPLAY": "your-value",
"RUST_LOG": "your-value"
}
}
}
}Run this in your terminal
claude mcp add terminal --env DISPLAY=your-value --env RUST_LOG=your-value -- npx -y mcp-server-terminalFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"terminal": {
"command": "npx",
"args": [
"-y",
"mcp-server-terminal"
],
"env": {
"DISPLAY": "your-value",
"RUST_LOG": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"terminal": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-server-terminal"
],
"env": {
"DISPLAY": "your-value",
"RUST_LOG": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
DISPLAY envRUST_LOG envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account aybelatchane, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.3) reached the registry 11 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
MCP server for browser use access
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MCP server enabling AI agents to interact with terminal applications through structured Terminal State Tree representation. Works with any AI assistant that supports the Model Context Protocol.
npx mcp-server-terminal
Download pre-built binaries from Releases.
git clone https://github.com/aybelatchane/mcp-server-terminal.git
cd mcp-server-terminal cargo build --release
claude mcp add terminal -- npx mcp-server-terminal
Add to ~/.claude.json (macOS/Linux) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": { "terminal": { "command": "npx", "args": ["mcp-server-terminal"] } } }
codex mcp add terminal -- npx mcp-server-terminal
Add to ~/.codex/config.toml:
[mcp_servers.terminal]
command = "npx" args = ["mcp-server-terminal"]
gemini mcp add terminal npx mcp-server-terminal
VS Code 1.101+ supports MCP. Add to your VS Code settings (settings.json):
{
"mcp.servers": { "terminal": { "command": "npx", "args": ["mcp-server-terminal"] } } }
Add to ~/.cursor/mcp.json or .cursor/mcp.json in your project:
{
"mcpServers": { "terminal": { "command": "npx", "args": ["mcp-server-terminal"] } } }
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": { "terminal": { "command": "npx", "args": ["mcp-server-terminal"] } } }
Add to your Zed settings (Preferences → Settings):
{
"context_servers": { "terminal": { "command": { "path": "npx", "args": ["mcp-server-terminal"] } } } }
Click MCP Servers icon → Configure → Advanced MCP Settings, then add:
{
"mcpServers": { "terminal": { "command": "npx", "args": ["mcp-server-terminal"] } } }
Add to your Bedrock agent MCP configuration:
{
"mcpServers": { "terminal": { "command": "npx", "args": ["mcp-server-terminal"] } } }
For any MCP-compatible client, configure the server with:
npx["mcp-server-terminal"]Or if using the binary directly:
terminal-mcpAsk your AI agent:
| Tool | Description |
|---|---|
terminal_session_create | Start a terminal session |
terminal_session_list | List active sessions |
terminal_session_close | Close a session |
terminal_session_resize | Resize terminal dimensions |
terminal_snapshot | Capture terminal state with UI elements |
terminal_type | Type text into terminal |
terminal_press_key | Press keys (arrows, F-keys, Ctrl+X) |
terminal_click | Click on detected UI element |
terminal_wait_for | Wait for text, element, or idle state |
terminal_read_output | Read raw terminal output |
By default, sessions spawn a visible terminal window (xterm). For headless operation:
npx mcp-server-terminal --headless
Or in your MCP config:
{
"mcpServers": { "terminal": { "command": "npx", "args": ["mcp-server-terminal", "--headless"] } } }
Visual mode requires X11. Add the DISPLAY environment variable to your MCP config:
{
"mcpServers": { "terminal": { "command": "npx", "args": ["mcp-server-terminal"], "env": { "DISPLAY": ":0" } } } }
Set the RUST_LOG environment variable:
{
"mcpServers": { "terminal": { "command": "npx", "args": ["mcp-server-terminal"], "env": { "RUST_LOG": "info" } } } }
Log levels: error, warn, info, debug, trace
Logs go to stderr (stdout is reserved for MCP protocol).
| Platform | Architecture | Status | Visual Mode |
|---|---|---|---|
| Linux | x64, arm64 | ✅ Full support | xterm + tmux |
| macOS | x64, arm64 | ✅ Full support | Terminal.app / iTerm2 |
| Windows (WSL) | x64, arm64 | ✅ Full support | xterm + tmux (via X11) |
| Windows (native) | x64 | ⚠️ Headless only | Not supported |
Windows users: Use WSL for full functionality including visual mode.
MIT