agentgrasp

Official registry Search and web

Yes/no questions about local files, and relevant-file search, with TypeSafe Jev

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

CARGO package agentgrasp

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. agentgrasp
  2. Install
  3. Settings
  4. Costs and risks
  5. Links

agentgrasp

agentgrasp keeps long command output out of a Claude Code agent's context. Claude Code still runs every Bash command. When the output is long, agentgrasp saves it to a file and the agent sees a short summary with the file path. The agent can then read the file, or ask yes/no questions about it with the ask tool. The search tool finds the files and line ranges that are relevant to a question, without returning source text.

ask and search use Jev, TypeSafe's yes/no model.

Install

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/damejeras/agentgrasp/releases/latest/download/agentgrasp-installer.sh | sh
claude plugin marketplace add damejeras/agentgrasp
claude plugin install agentgrasp@agentgrasp

Instead of the installer, npm install -g agentgrasp installs the same binary, and npx agentgrasp mcp runs the MCP server without a global install.

The plugin calls agentgrasp from PATH. Set TYPESAFE_API_KEY in the environment that starts Claude Code; without it, ask and search return provider_unavailable.

Settings

agentgrasp runs each Bash command inside a { ... } group that sends its output to files. Claude Code asks for approval of every command that holds such a group, also when your allow rules allow the command, and no allow rule changes that. So in Claude Code's default and acceptEdits permission modes, every Bash call asks for approval. In bypassPermissions mode the calls run without a prompt. Your deny rules still block a command in every mode.

When the Claude Code sandbox is on, let Bash write the agentgrasp state directory. Without this, the output cannot go to its files, the shell prints the error, and the command does not run:

{
  "sandbox": {
    "filesystem": {
      "allowWrite": ["~/.local/state/agentgrasp"]
    }
  }
}

Use $XDG_STATE_HOME/agentgrasp instead when XDG_STATE_HOME is set.

Costs and risks

  • ask and search send file content to TypeSafe. TypeSafe lists Jev at $42 per billion input tokens. Each call writes the tokens it used to its record under ~/.local/state/agentgrasp/asks/ or searches/.
  • ask and search can read any file inside the MCP roots, which are the project directory and the directories you add. This includes files that your Read deny rules block. When you allow these tools, you allow that.
  • The state directory grows until you delete files from it. agentgrasp never deletes them.
  • A runaway command can fill the disk until Claude Code's timeout stops it.
  • MCP Registry name: mcp-name: io.github.damejeras/agentgrasp

Frequently asked questions

What is agentgrasp?

Yes/no questions about local files, and relevant-file search, with TypeSafe Jev

How do I install agentgrasp?

Follow the installation steps in its documentation, shown on this page and in its repository.

Does agentgrasp need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is agentgrasp open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains agentgrasp?

It is published by damejeras. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.