Forge logo

Forge

by ferodrigop

Manages persistent PTY sessions, terminal output, local coding agents, and concurrent development workflows over MCP.

Install Forge

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "ferodrigop-forge": {
      "command": "npx",
      "args": [
        "-y",
        "forge-terminal-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 25 tools correctly (1mo ago).

Overview

The ferodrigop/forge MCP server gives AI coding agents persistent PTY terminals they can create, control, monitor, and close. It uses incremental ring-buffer reads, rendered screen capture, event subscriptions, templates, and grouped sessions to manage concurrent work. Agents can also launch Claude, Codex, and Gemini CLI sessions or delegate one-shot and interactive tasks. Reach for it when an MCP client needs long-running development processes, parallel builds, interactive commands, or terminal-based agent orchestration.

Use cases

  • Run development servers and test suites concurrently
  • Monitor long-running terminal processes incrementally
  • Delegate coding tasks to Claude, Codex, or Gemini agents
  • Capture clean terminal screen state for an agent
  • Run one-off build and installation commands

Key features

  • Persistent PTY terminal sessions
  • Incremental ring-buffer output reads
  • Headless terminal viewport capture
  • Claude, Codex, and Gemini agent spawning
  • Session templates, groups, and event subscriptions
  • Real-time web dashboard

Tools25

What Forge lets your agent do. Expand a tool for its parameters.

Verified live~4.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

19/19 checks healthy over the last 80d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · forge-terminal-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars28Stargazers on the source repository.
npm downloads65Package downloads in the last 30 days.
Last commit6mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed25Callable tools this server registers over MCP.
Directory activity7 viewsConfig copies, upvotes, and views on AllMCPs.

How Forge works

What ferodrigop/forge MCP server does

The ferodrigop/forge MCP server exposes real terminal sessions through the Model Context Protocol. Each session runs in a pseudo-terminal, allowing interactive programs, colored output, and terminal user interfaces to operate as they would in a normal terminal. Agents can create sessions with commands, working directories, names, tags, dimensions, and buffer settings, then reuse the returned session IDs for later operations.

It supports both long-lived workflows and disposable commands. run_command creates a session, waits for the process to finish, returns its output, and cleans up automatically. Persistent sessions are suited to development servers, test watchers, shells, and other processes that need follow-up input.

How it works

The ferodrigop/forge MCP server keeps terminal output in a ring buffer and tracks read positions per consumer. read_terminal therefore returns output added since the previous read rather than repeatedly returning the complete buffer. read_screen instead returns the current viewport as rendered text without ANSI escape sequences. grep_terminal searches buffered output with a regular expression, while wait_for can block until a pattern appears or a process exits.

Sessions can be monitored individually or in batches with read_multiple, filtered by tags, and grouped for cleanup. Event subscriptions emit MCP logging notifications when a session exits or matches a pattern. Terminal input can be written as text or sent as control sequences such as Ctrl+C, arrow keys, Enter, and Tab. The server also reports uptime, version, session count, and memory usage through health_check.

Setup and configuration

Install the published package with a package manager that provides npx, then start the local daemon:

Terminal
npx forge-terminal-mcp start -d

The documented HTTP endpoint is http://127.0.0.1:3141/mcp. Clients connect to that endpoint after the daemon starts. A dashboard can be enabled with --dashboard, and the listening port can be changed with --port; the MCP client URL must match the selected port.

The project requires Node.js 18 or newer when using its npm installation path. MCP clients load server configuration at process startup, so clients need to be restarted after adding or removing the server.

Tools and capabilities

The tool set covers:

  • Creating, reviving, listing, resizing, writing to, and closing PTY sessions.
  • Starting sessions from templates such as shell, Next.js development, Vite development, and npm test.
  • Launching Claude Code, Codex, and Gemini CLI agents in interactive or one-shot modes.
  • Running delegated tasks in one-shot or multi-turn interactive mode.
  • Monitoring output with incremental reads, screen capture, regex searches, waits, and event subscriptions.
  • Reviewing or clearing persisted Claude and Codex session history.
  • Running a real-time browser dashboard for terminal activity and past chat sessions.

When launching an agent session, the working directory must be supplied explicitly. Claude Code sessions can use a worktree and branch for isolated Git work; one-shot modes require the relevant prompt where documented.

Limitations and notes

The material describes a local daemon and local HTTP MCP endpoint rather than a hosted service. It does not document authentication, remote hosting, or environment variables. Commands executed through terminal sessions depend on the tools and permissions available in the host environment. Interactive agent sessions remain alive for follow-up work, while one-shot execution exits after processing its prompt. Forge is MIT-licensed.

The ferodrigop/forge MCP server is intended for MCP-compatible clients, with setup examples for Claude Code, Codex, and Gemini CLI. Those clients must be restarted when their MCP configuration changes.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Forge

Run `npx forge-terminal-mcp start -d` to start the local daemon, then configure an MCP client to use its HTTP endpoint.

Yes. The README provides Claude Code setup using the HTTP endpoint `http://127.0.0.1:3141/mcp`.

Yes. It can create and monitor multiple tagged sessions, read several sessions together, and close all sessions in a matching group.

Yes. Separate tools spawn Claude Code, Codex, and Gemini CLI sessions, with interactive and one-shot modes.

No credential requirement or API key configuration is documented. The project describes a zero-configuration local setup.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewForge AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ferodrigop-forge?style=directory)](https://allmcps.com/mcp/ferodrigop-forge)
HTML Embed
<a href="https://allmcps.com/mcp/ferodrigop-forge"><img src="https://allmcps.com/api/badge/ferodrigop-forge?style=directory" alt="Forge on AllMCPs" /></a>