Terminator

Created By
iris-networksa year ago
A lightweight Model Context Protocol (MCP) server written in Go that enables secure terminal command execution on macOS and Linux. Supports persistent shell sessions, configurable timeouts, and both HTTP (StreamableHTTP) and STDIO transports. Designed for AI integrations and automation use cases with flexible session management and platform-aware execution.
Overview

What is Terminator?

Terminator is a lightweight Model Context Protocol (MCP) server written in Go that enables secure terminal command execution on macOS and Linux, designed for AI integrations and automation use cases.

How to use Terminator?

To use Terminator, build the server using make build, then run it in HTTP mode with ./mcp-terminal-server --http --port 8080 or in STDIO mode with ./mcp-terminal-server. You can test its functionality using curl commands to interact with the MCP endpoints.

Key features of Terminator?

  • Cross-platform support for macOS and Linux
  • Configurable timeouts for command execution
  • Secure execution in a controlled environment
  • Flexible shell support and multiple transport modes (STDIO and StreamableHTTP)
  • Persistent shell sessions to maintain state between commands

Use cases of Terminator?

  1. Automating terminal commands in development environments
  2. Integrating with AI systems for automated command execution
  3. Managing shell sessions for various applications

FAQ from Terminator?

  • Is Terminator secure?

Yes! It runs commands in a controlled environment with proper error handling.

  • Can I use Terminator on Windows?

No, Terminator is designed specifically for macOS and Linux.

  • How do I manage sessions?

You can manage sessions using the session_manager tool provided by the server.

Server Config

{
  "mcpServers": {
    "terminal": {
      "type": "streamable-http",
      "url": "http://localhost:8080/mcp",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-p",
        "8080:8080",
        "-e",
        "MCP_COMMAND_TIMEOUT=30",
        "-e",
        "MCP_SHELL=/bin/bash",
        "shanurcsenitap/terminator:latest",
        "--http",
        "--host",
        "0.0.0.0",
        "--port",
        "8080"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
iris-networks
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago