Suvadu MCP

MCP server and shell history replacement: a SQLite command log with context that agents read over MCP

  • 128 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

Why this level

  • Stores command and prompt history, which can contain secrets, and the MCP server exposes it to agents.
All reasons and checks

appachitech/suvadu

Install

Manual install

brew tap AppachiTech/suvadu && brew install suvadu

The first command of the Install section. macOS and Linux also have a script and `cargo install suvadu`.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Stores command and prompt history, which can contain secrets, and the MCP server exposes it to agents.

This is third-party code. Review the repository files before installing.

What it does

Suvadu replaces shell history with a SQLite store. Every command is recorded with its exit code, duration, directory, executor and session. Search covers the whole history through `Ctrl+R`, and data stays on the machine. The built-in MCP server hands agents 22 read tools, 8 resources and 6 prompts: session discovery, project context, failure analysis, check of dangerous commands, a shared skills library and saved command templates. Two write tools stay off until the user turns them on. The tool tracks sessions of Claude Code, Codex, OpenCode and Cursor, and only tags commands for Windsurf, Aider, Continue and Copilot.

Who it is for. Terminal developers who run several AI agents and want shared memory of commands, runs and failures.

Good fit when

  • An agent needs to know which commands already ran in the project and how they ended.
  • You want to trace past failures: which command failed and after which prompt.
  • Shell history should be searchable by directory, exit code and duration.
  • Several agents (Claude Code, Codex, Cursor) share one view of sessions.

Not a fit when

  • You need history synced across machines through a cloud.
  • The shell is not zsh or bash and the hook cannot be installed.
  • You want an agent that edits files rather than one that reads history.

Example request

Show the commands that failed in this project over the last week and the agent prompt before each.

MCP

Transport
stdio
Authentication
not required

Limitations

The utility adds a hook to `~/.zshrc` or `~/.bashrc`, shows the line before writing and asks for confirmation. The user decides whether to enable the two MCP write tools. Once a day the program checks for a new release, and that check can be turned off. Windows is not mentioned in the install section. The speed figures (207 microseconds to record a command at 100,000 entries) come from one run on one machine, and the author says so. Full session capture is not available for every agent: Cursor has no token usage.

How to disable. Remove the hook block from `~/.zshrc` or `~/.bashrc` and delete the MCP entry from the client. Clear the SQLite history database by hand.

FAQ

How do I run the Suvadu MCP server?

`suvadu mcp-serve` (or `suv mcp-serve`) starts a stdio server. Add it to the MCP client configuration.

Does Suvadu send data to a cloud?

No, everything is local, with no cloud, telemetry or account. The only request it makes on its own is a once-a-day release check.

Can agents modify history?

Not by default. The two write tools turn on only when the user opts in.

Which agents are tracked in full?

Claude Code, Codex, OpenCode and Cursor sessions (Cursor without token usage). Other clients only get command tagging.

Which install methods exist?

Homebrew, an install script for macOS and Linux, and `cargo install suvadu` with Rust 1.95 or later.

Discussion

No questions or reviews yet.

An MCP server and CLI that find in Claude Code and Codex sessions why a file became what it is: who asked the agent what, when and what changed

MCP serverExtended access776Repository stars

The MCP endpoint of a Salt workspace on your server: an agent creates pages, databases and comments with a person rights.

MCP serverBroad access178Repository stars

Cunzhi (寸止)

寸止 (Cunzhi)

MCP server in Rust and Tauri: the agent shows a dialog with options before ending a reply, keeps project rules and searches code

MCP serverBroad access1.4KRepository stars
Official

Cross-device clipboard sync with a built-in MCP server: the agent reads your copy history, and data never leaves for the cloud

MCP serverExtended access2.7KRepository stars

An MCP server and Mac app that keeps one local index of repos, agent sessions and tickets, with semantic search and work threads

MCP serverExtended access76Repository stars

README in short

The Rust program stores history in SQLite and exposes it through a TUI and CLI. An MCP server serves agents, and the project has a site with CLI and MCP docs.

README badge

Report a problem