What is the key difference between Forge and Terminal History MCP?

Forge belongs to the Command Line category with local stdio execution, while Terminal History MCP belongs to the Command Line category with local stdio execution.

How do I install Forge or Terminal History MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Forge and Terminal History MCP free or paid?

Forge operates under a Free / Open Source model (No auth required). Terminal History MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Forge lists 25 tools with 4 views and 23 GitHub stars. Terminal History MCP lists 5 tools with 1 views and 4 GitHub stars.

Can I use both Forge and Terminal History MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Forge vs Terminal History MCP

In-depth architectural comparison of the Forge and Terminal History MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Forge

Command Line · Local stdio

Quality: 61/100 (Good) | Auth: No auth required

Terminal History MCP

Command Line · Local stdio

Quality: 60/100 (Good) | Auth: No auth required

Verdict Summary: Choose Forge if you need specialized Command Line tools running via a local process. Choose Terminal History MCP if your workspace requires Command Line integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Forge when:

You need dedicated capabilities in the Command Line domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: create_terminal, revive_terminal, create_from_template.

Explore Forge Details

Choose Terminal History MCP when:

You need dedicated capabilities in the Command Line domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: reindex, search_history, recent_in_dir.

Explore Terminal History MCP Details

Feature & Specification Comparison

Specification	Forge ferodrigop Command Line	Terminal History MCP HasanJahidul Command Line
Summary	Terminal MCP server for AI coding agents with persistent PTY sessions, ring-buffer incremental reads, headless xterm screen capture, multi-agent orchestration, and a real-time web dashboard.	Full-text search over your shell history (zsh / bash / fish) via SQLite FTS5. Local-only. 11-pattern secret redaction runs BEFORE insert. Captures cwd / exit code / duration via opt-in shell hook. Tools: searchhistory, recentindir, failedcommands, commandchains, reindex.
Category & Scope

Tools & Capabilities Breakdown

Forge Tools (25)

create_terminal

Spawn a new PTY terminal session. Returns session ID for subsequent operations.

revive_terminal

Recreate a previously exited terminal session with the same command, working directory, name, tags, and dimensions. The old session is removed and a fresh one is spawned.

create_from_template

Create a terminal session from a pre-configured template (e.g., shell, next-dev, vite-dev, npm-test).

list_templates

List all available session templates.

spawn_claude

Spawn a Claude Code agent in a new terminal session. IMPORTANT: cwd must be set explicitly — there is no session inheritance. By default runs in interactive mode — the session stays alive and accepts follow-up messages via the dashboard. Use oneShot: true for autonomous --print mode. Use worktree + branch to run in an isolated git worktree.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Forge Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "ferodrigop-forge": {
      "command": "npx",
      "args": [
        "-y",
        "forge-terminal-mcp"
      ]
    }
  }
}

Terminal History MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "hasanjahidul-terminal-history-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcpize"
      ]
    }
  }
}

Frequently Asked Questions

Forge is categorized under Command Line and uses a local stdio subprocess. In contrast, Terminal History MCP belongs to Command Line using local stdio subprocess. Select Forge when you need capabilities focused on command line and Terminal History MCP when you require tools for command line.

More alternatives to Forge More alternatives to Terminal History MCP Command Line category hub