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

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

Backburner 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?

Backburner lists 0 tools with 2 views and 2 GitHub stars. Terminal History MCP lists 5 tools with 1 views and 4 GitHub stars.

Can I use both Backburner 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

Backburner vs Terminal History MCP

In-depth architectural comparison of the Backburner 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

Backburner

Command Line · Local stdio

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

Terminal History MCP

Command Line · Local stdio

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

Verdict Summary: Choose Backburner 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 Backburner 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).

Explore Backburner 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	Backburner Command Line	Terminal History MCP HasanJahidul Command Line
Summary	Run long shell commands as background tasks: start them, keep working, collect the results later	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	Command Line

Tools & Capabilities Breakdown

Backburner Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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.

search_history

Read-only. Full-text search (SQLite FTS5, stemmed, Unicode-aware) over all indexed shell commands. Supports keyword and prefix queries — e.g. `docker build`, `git reb*`. Returns the most recent matches first, each with timestamp, shell, cwd, and exit code when available. Local index only; nothing is sent anywhere. If a query returns nothing you may need `reindex` first.

recent_in_dir

Read-only. Lists the most recent commands that were run with a given working directory — answers "what was I doing in this project?". Requires the shell hook to have been installed (legacy entries have no cwd and won't appear). Returns newest first with timestamps and exit codes. Local index only.

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

Backburner Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "backburner": {
      "command": "uvx",
      "args": [
        "backburner-mcp"
      ]
    }
  }
}

Terminal History MCP Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

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