GitWarren

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/klarluft-gitwarren

About

Use cases: code-review, version-control

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 25, 2026.

Tools

5 read · 9 write · 3 delete

Secrets

None asked for

Install scripts

Runs code on install

Runs as

Node.js package

Tools (17)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• add_repositoryAdd repository

  Start tracking a git repository. `path` may be any directory inside the working tree - it is resolved to the repository root before being stored, so the same repository cannot be added twice under two different paths. `name` defaults to the folder name. Fails with NOT_A_GIT_REPOSITORY if the path is not inside a git repository.

• add_review_commentAdd review comment

  Start a new discussion on a review. Omit `filePath` and `line` for a comment on the review as a whole; give both to attach it to a line, the way a pull-request review comment works. `side` picks which side of the diff `line` counts on - "head" (the default) for the code as it will be, "base" to remark on a line the change removed. Add `startLine` to comment on a block rather than a single line; `line` is then the last line of it, and the one the whole range follows if the code moves. The line is not required to be part of the diff. A line the patch does not print is looked up in the file itsel…

• agent_identityAgent identity

  Show how comments from this session will be attributed, and optionally set a label for the session. The tool name ("Claude Code", "Codex", ...) is taken from the MCP handshake and cannot be changed - it is what makes attribution consistent across sessions. `label` is a short handle for *this* session ("auth-refactor"), worth setting when more than one agent is working the same review; it is remembered until this server process exits.

• create_reviewCreate review

  Open a review comparing two refs in a tracked repository. `baseRef` is what the changes are measured against (usually the trunk) and `headRef` is the branch under review; the diff is taken from their merge base, like a pull request. Both refs must exist and share history, or the call fails with INVALID_INPUT. `title` defaults to "<head> into <base>". If the head branch is checked out in a worktree, its uncommitted changes are part of the review as well - a review can be opened on work that has never been committed. Passing the same ref as both endpoints is allowed and does exactly that: the re…

• delete_review_commentDelete a commentcan change or delete data

  Delete one message. If it was the only message in its thread, the thread goes with it. As with editing, an agent can only delete messages written by its own tool.

• get_repositoryGet repositoryread-only

  Fetch one tracked repository by id, with its live git state.

• get_reviewGet reviewread-only

  Fetch one review by id, with the repository it belongs to attached (including the repository path, so the changes can be inspected with git directly). Each result carries `guiUrl`, a link that opens this in GitWarren. Show it to the user - it exists to be clicked, and it is how they see this without going and finding it themselves. The link works whether or not GitWarren is running right now, so hand it over without checking anything. If the user says it will not open - the browser reports that the connection was refused - then GitWarren is not running on their machine, and starting it makes …

• list_repositoriesList repositoriesread-only

  List every git repository tracked in GitWarren, each with its live git state (whether the folder still exists, whether it is still a repository, and the current branch). Git state is read fresh on every call and is never cached.

• list_review_commentsList review commentsread-only

  Every discussion on a review: review-level threads and line comments alike, each with its full message history and who wrote each message. Line threads also carry an `anchor` saying where they land in the code as it stands right now - "anchored" (the line is unchanged), "moved" (the code shifted and `anchor.line` is its current line) or "outdated" (the line is gone, so the comment may be about code that has since been rewritten). Threads about files the diff does not contain are resolved against those files at the head rather than against the patch, so a comment on unchanged code reports an ho…

• list_reviewsList reviewsread-only

  List reviews, newest activity first. Filter with `repositoryId` and/or `status` ("open" or "closed"); omit both to list every review across all tracked repositories. A review records the two refs being compared, not the commits they resolved to - read the repository with git to see the actual changes. Each result carries `guiUrl`, a link that opens this in GitWarren. Show it to the user - it exists to be clicked, and it is how they see this without going and finding it themselves. The link works whether or not GitWarren is running right now, so hand it over without checking anything. If the u…

• remove_repositoryRemove repositorycan change or delete data

  Stop tracking a repository. This only removes it from GitWarren - the working copy on disk is never touched.

• remove_reviewRemove reviewcan change or delete data

  Delete a review. This removes only the review record - no branch, commit or file in the repository is touched. To file a finished review away without deleting it, set its status to "closed" instead.

• reply_to_review_commentReply to a review comment

  Add a message to an existing thread. Use this rather than opening a new thread when responding to something someone already raised, so the discussion stays in one place. Thread ids come from `list_review_comments`. To include a screenshot, write the file to disk first, then reference it as an ordinary markdown image: The dropdown renders behind the modal:  The file is copied into GitWarren and the path rewritten, so the image survives /tmp being cleaned. Always write alt text - it is what agents without vision see. If the path contain…

• resolve_review_commentResolve or reopen a thread

  Mark a discussion settled, or reopen one. Set `resolved` to true once the point has been addressed, false to bring it back. Resolving records who did it; it never deletes the messages, which stay readable. Each result carries `guiUrl`, a link that opens this in GitWarren. Show it to the user - it exists to be clicked, and it is how they see this without going and finding it themselves. The link works whether or not GitWarren is running right now, so hand it over without checking anything. If the user says it will not open - the browser reports that the connection was refused - then GitWarren …

• update_repositoryUpdate repository

  Rename a tracked repository, or repoint it at a moved working copy. Provide at least one of `name` or `path`. A new path is validated and resolved exactly as it is when adding.

Signals

Stars

18

Forks

2

Open issues

0

Last commit

Oct 14, 2026 (14 days ago)

Last release

Oct 14, 2026 (14 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.klarluft/gitwarren

Version

1.0.1

Auth

No auth

Packages

npm gitwarren

License

GPL-3.0

Repository

github.com/klarluft/gitwarren-app

Website

gitwarren.com

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql