# GitVerse MCP [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/grigoriy-grisha/gitverse-mcp  
**GitHub Stars:** 1  
**npm Downloads (last month):** 333  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/grigoriy-grisha-gitverse-mcp

## Description
MCP server for GitVerse: repositories, pull requests, reviews, comments and CI

## Tools
Capabilities this server exposes over MCP:

- **listRepositories** — List repositories. Without arguments lists the authenticated user's repositories; pass org to list organization repositories. Supports page/per_page.
- **getRepository** — Get details of a specific repository.
- **getPullRequests** — List pull requests of a repository. state filters by open/closed. Supports page/per_page.
- **createPullRequest** — Create a pull request from head to base. GitVerse has no reviewer requests — use assignees instead. Pass draft=true to create a draft.
- **getPullRequest** — Get details of a specific pull request.
- **updatePullRequest** — Update a pull request: title, body, state (open|closed), base branch. assignees and labels are applied through the issue endpoint because a PR is an issue in GitVerse.
- **getPullRequestActivity** — Get the activity/timeline of a pull request.
- **approvePullRequest** — Approve a pull request by submitting an APPROVED review.
- **unapprovePullRequest** — Remove your approval: finds your latest APPROVED review on the pull request and deletes it.
- **declinePullRequest** — Decline (close) a pull request. An optional message is posted to the discussion before closing.
- **requestChanges** — Request changes on a pull request by submitting a REQUEST_CHANGES review.
- **removeChangeRequest** — Remove your change request by superseding it with an APPROVED review (GitVerse has no dedicated un-request endpoint).
- **createDraftPullRequest** — Create a draft pull request (equivalent to createPullRequest with draft=true).
- **getPullRequestComments** — List discussion comments on a pull request. Supports since/before filters.
- **addPullRequestComment** — Comment on a pull request. Without inline — a general discussion comment. With inline {path, to} — an inline review comment on line `to` of the diff (commit SHA is resolved automatically). Replying: pass reply_to with a comment id.
- **getPullRequestReviews** — List reviews of a pull request (id, state APPROVED/REQUEST_CHANGES/COMMENT, author). Review comments themselves are not exposed by the GitVerse public API.
- **replyPullRequestReviewComment** — Reply inside an existing inline review thread of a pull request. comment_id is the id of any comment of the thread (the number in the #comment-<id> anchor of the PR web page). Works through in_reply_to: POST /pulls/{n}/comments.
- **updatePullRequestComment** — Edit a discussion comment on a pull request.
- **deletePullRequestComment** — Delete a discussion comment on a pull request.
- **getPullRequestDiff** — Get the changed files of a pull request, including per-file patches.
- **getPullRequestCommits** — List the commits of a pull request. Supports page/per_page.
- **listPipelineRuns** — List CI runs (GitVerse Actions, Bitbucket Pipelines analog). Filters: status, branch, event. Supports page/per_page.
- **getPipelineRun** — Get details of a CI run.
- **runPipeline** — Trigger a CI run of a workflow on a branch or tag.
- **getPipelineSteps** — List jobs (steps) of a CI run.
- **getPipelineStep** — Get details of a CI job (step).
- **getPipelineStepLogs** — Get logs of a CI job (step).

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "gitverse-mcp": {
    "command": "npx",
    "args": ["-y","@grigoriy-grisha/gitverse-mcp@latest"],
    "env": {
      "GITVERSE_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `GITVERSE_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What GitVerse MCP MCP server does

GitVerse MCP MCP server gives AI assistants access to repositories hosted on GitVerse, the Russian repository hosting service. Its 25 tools cover repository discovery, pull request management, code review, discussion comments, assignments, labels, and GitVerse Actions CI.

Repository tools can list a user's repositories or an organization's repositories and retrieve a repository record. Pull request tools support listing by state, creating regular or draft requests, editing metadata, and reading commits, changed files, and activity. Review tools can place inline comments on diff lines and manage discussion comments. They also support approval, requesting changes, declining a pull request, and removing the current user's approval or change request.

The CI tool group works with GitVerse Actions runs. It can list runs with filters, retrieve a run, start a workflow, inspect its jobs, and read job logs. In GitVerse, a pull request also behaves as an issue for assignees and labels, so creation and update operations can set those values.

## How it works

The server implements the Model Context Protocol and sends requests to the official GitVerse public REST API. It adds the required Bearer authorization and GitVerse vendor media-type headers automatically, so MCP tool calls do not require callers to construct those headers themselves. Requests that receive HTTP 429 are retried up to three times while honoring the API's `Retry-After` value.

List operations support optional pagination through `page` and `per_page` parameters. Pull request listing accepts `open` or `closed` state filters. The server uses GitVerse's API rather than a local repository checkout, so the available data and actions depend on the authenticated account and the permissions granted to its token.

## Setup and configuration

Node.js 20 or newer is required. The package can be run directly with `npx` or installed globally or inside a project with npm. Set `GITVERSE_TOKEN` to a personal GitVerse token before starting the process. The token should include repository read and write access, issue and pull request read and write access, and CI/CD read and write access when pipeline tools are needed.

`GITVERSE_BASE_URL` optionally changes the API base, which defaults to `https://api.gitverse.ru`. `GITVERSE_API_VERSION` optionally changes the vendor media-type version and defaults to `1`. Cursor and Claude Desktop can start the server through an MCP configuration using `npx` and the token in the process environment. Local development can instead launch the built `dist/index.js` file with Node.js.

## Tools and capabilities

The available tools are grouped as follows:

- Repositories: `listRepositories`, `getRepository`
- Pull requests: create, draft, retrieve, update, list, inspect activity, commits, and diffs
- Review decisions: approve, remove approval, request changes, remove a change request, and decline
- Comments: list, add, edit, and delete pull request comments
- CI: list and inspect pipeline runs, start a pipeline, inspect steps, and retrieve step logs

GitVerse MCP MCP server is suited to the Version Control category when an agent must examine or change GitVerse work without switching to separate repository, review, or CI tools.

## Limitations and notes

GitVerse's API does not provide a separate reviewer-request operation; use pull request assignees instead. The API rate limit is 2,000 requests per user per hour. Automatic retries help with temporary 429 responses but do not remove the limit. A token without the required write scopes cannot perform review, comment, pull request, or CI mutations. The project is licensed under MIT.

_Full upstream README: https://allmcps.com/mcp/grigoriy-grisha-gitverse-mcp/readme_