mcpField
A
agentgrasp

agentgrasp

Local
github.com/damejerasDeveloper Tools0Updated 4w ago

About agentgrasp

agentgrasp is an MCP server and Claude Code plugin that keeps lengthy Bash output out of the agent's context by saving it to files and returning a short summary. Its `ask` and `search` tools use TypeSafe's Jev model to answer yes/no questions about files and find relevant files and line ranges without returning source text.

Key features

  1. 01Save long command output to files
  2. 02Return summaries with file paths
  3. 03Ask yes/no questions about files
  4. 04Find relevant files and line ranges
  5. 05Use TypeSafe Jev for ask and search

Use cases

  1. 01Keep lengthy shell output out of agent context
  2. 02Check a file's contents with a yes/no question
  3. 03Locate relevant file sections without returning source

MCP support

It can run as an MCP server via `npx agentgrasp mcp`. The `ask` and `search` tools operate on files within configured MCP roots; using them sends file content to TypeSafe.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository
Packages
cargoagentgrasp0.1.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

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.

Links

  • MCP Registry name: mcp-name: io.github.damejeras/agentgrasp

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.