What is the key difference between Cli MCP Server and Terminal History MCP?

Cli MCP Server 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 Cli MCP Server 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 Cli MCP Server and Terminal History MCP free or paid?

Cli MCP Server 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?

Cli MCP Server lists 6 tools with 3 views and 178 GitHub stars. Terminal History MCP lists 5 tools with 1 views and 4 GitHub stars.

Can I use both Cli MCP Server 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

Cli MCP Server vs Terminal History MCP

In-depth architectural comparison of the Cli MCP Server 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

Cli MCP Server

Command Line · Local stdio

Quality: 40/100 (Fair) | Auth: No auth required

Terminal History MCP

Command Line · Local stdio

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

Verdict Summary: Choose Cli MCP Server 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 Cli MCP Server 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).
You have access to required keys: ALLOWED_DIR, ALLOWED_COMMANDS, ALLOWED_FLAGS, MAX_COMMAND_LENGTH, COMMAND_TIMEOUT, ALLOW_SHELL_OPERATORS.
Primary tools included: Whitelisted command execution, Configurable flag validation, Restricted working-directory access.

Explore Cli MCP Server 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: .

Feature & Specification Comparison

Specification	Cli MCP Server MladenSU Command Line	Terminal History MCP HasanJahidul Command Line
Summary	Command line interface with secure execution and customizable security policies	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

Cli MCP Server Tools (6)

Whitelisted command execution

Configurable flag validation

Restricted working-directory access

Path traversal and symlink checks

Shell operator blocking

Timeout and command-length limits

Terminal History MCP Tools (5)

reindex

Re-parses the local shell history files (`~/.zsh_history`, `~/.bash_history`) and the hook's extended log into the SQLite index. Idempotent — already-indexed commands are skipped by hash, so it is safe to call repeatedly. Run it after a burst of shell activity to make recent commands searchable. Reads only local files; writes only to `~/.terminal-history-mcp/`. Takes no arguments. Returns counts of parsed / inserted / skipped entries.

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).

Cli MCP Server Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mladensu-cli-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mladensu-cli-mcp-server"
      ],
      "env": {
        "ALLOWED_DIR": "YOUR_ALLOWED_DIR_HERE",
        "ALLOWED_COMMANDS": "YOUR_ALLOWED_COMMANDS_HERE",
        "ALLOWED_FLAGS": "YOUR_ALLOWED_FLAGS_HERE",
        "MAX_COMMAND_LENGTH": "YOUR_MAX_COMMAND_LENGTH_HERE",
        "COMMAND_TIMEOUT": "YOUR_COMMAND_TIMEOUT_HERE",
        "ALLOW_SHELL_OPERATORS": "YOUR_ALLOW_SHELL_OPERATORS_HERE"
      }
    }
  }
}

Terminal History MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Cli MCP Server 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 Cli MCP Server when you need capabilities focused on command line and Terminal History MCP when you require tools for command line.

More alternatives to Cli MCP Server More alternatives to Terminal History MCP Command Line category hub Canonical compare URL