Terminal History MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| reindexA | Re-parse ~/.zsh_history and ~/.bash_history into the local index. Run after new shell activity. |
| search_historyA | Full-text search across indexed shell history. Returns matching commands with timestamp/cwd/exit code. |
| recent_in_dirB | List recent commands run in a specific working directory (requires cwd capture, may be empty for legacy entries). |
| failed_commandsC | Recent commands with non-zero exit code. Useful for debugging recent shell errors. |
| command_chainsB | For each match of query, return commands run within ±5 min — reveals multi-step sequences (cd → build → deploy). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/HasanJahidul/terminal-history-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server