GitVerse MCP

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.