Terminal history MCP: MCP server, setup and security

What Terminal history MCP does

According to its repository: “Local full-text search over zsh, bash and fish history, with secret redaction and optional capture of cwd, exit code and duration.”

The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. Terminal history MCP is listed under Terminal and OS, a category of 115 servers in the directory, where it ranks #114 by stars.

Topics declared by the repository: claude, cli, fts5, shell-history, sqlite, terminal.

Installing and connecting Terminal history MCP

No package or remote server is declared in the official MCP registry: you install it from source, following the repository README.

It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: TypeScript. Listed systems: macOS, Linux.

Security: what to check

Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.

Points found for Terminal history MCP:

• System access: the Terminal and OS category gives the agent control over files, a terminal, code or a browser. A booby-trapped instruction in content the agent reads (prompt injection) can then turn into an action.

Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.

Project activity and maintenance

Created on May 8, 2026, the HasanJahidul/terminal-history-mcp repository has 5 stars and 0 forks, with 0 open issues. It has more stars than 13% of the servers in the directory. Last change 6 months ago.

Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.