SkillFoxx

Type a name, a task or a service

GitVerse MCP: code review and PRs

GitVerse MCP Server

A GitVerse MCP server with 25 bitbucket-mcp-style tools: pull requests, inline code review with verdicts and running GitVerse Actions CI pipelines

MCP server

High risk

We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.

Why this level

  • It can set review verdicts, write and delete comments, and trigger CI pipelines under the token owner's identity
  • The personal token grants repository access under the rights of the user who created it
All reasons and checks
Russian stack

grigoriy-grisha/gitverse-mcpAuthor:grigoriy-grisha

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/gitverse-mcp-server

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

This entry is high risk, so there is no one-click install. Review the code and add the config by hand.

Run in a terminal

claude mcp add --transport stdio --env 'GITVERSE_TOKEN=<your GITVERSE_TOKEN>' gitverse -- npx -y @grigoriy-grisha/gitverse-mcp@latest

Or add to the file .mcp.json, in the project

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

If the file already exists, add the server inside the mcpServers key.

Keys and settings

GITVERSE_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.cursor/mcp.json, for all projects

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

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

GITVERSE_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

code --add-mcp '{"name":"gitverse","type":"stdio","command":"npx","args":["-y","@grigoriy-grisha/gitverse-mcp@latest"],"env":{"GITVERSE_TOKEN":"<your GITVERSE_TOKEN>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "gitverse": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@grigoriy-grisha/gitverse-mcp@latest"
      ],
      "env": {
        "GITVERSE_TOKEN": "<your GITVERSE_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

GITVERSE_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add gitverse --env 'GITVERSE_TOKEN=<your GITVERSE_TOKEN>' -- npx -y @grigoriy-grisha/gitverse-mcp@latest

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.gitverse]
command = "npx"
args = ["-y", "@grigoriy-grisha/gitverse-mcp@latest"]
env = { GITVERSE_TOKEN = "<your GITVERSE_TOKEN>" }

If the file already exists, append the block to the end.

Keys and settings

GITVERSE_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.gemini/settings.json, for all projects

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

If the file already exists, add the server inside the mcpServers key.

Keys and settings

GITVERSE_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

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

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

GITVERSE_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

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

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

GITVERSE_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

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

If the file already exists, add the server inside the mcpServers key.

Keys and settings

GITVERSE_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "gitverse": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@grigoriy-grisha/gitverse-mcp@latest"
      ],
      "environment": {
        "GITVERSE_TOKEN": "<your GITVERSE_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

GITVERSE_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "gitverse": {
      "command": "npx",
      "args": [
        "-y",
        "@grigoriy-grisha/gitverse-mcp@latest"
      ],
      "env": {
        "GITVERSE_TOKEN": "<your GITVERSE_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

GITVERSE_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .codeassistant/mcp.json, in the project

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

If the file already exists, add the server inside the mcpServers key.

Keys and settings

GITVERSE_TOKENsecret, required

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit 08747cd.

Text for your agent

Create a personal token in GitVerse (Settings, token management) with rights for repositories, pull requests and CI/CD, then run the server with GITVERSE_TOKEN=token npx -y @grigoriy-grisha/gitverse-mcp@latest.

Other ways from the author
GITVERSE_TOKEN="ваш-токен" npx -y @grigoriy-grisha/gitverse-mcp@latest

Run without a global install.

This is third-party code. Review the repository files before installing.

What it does

The server gives access to GitVerse, a Russian repository-hosting service, through its official public REST API. Tools cover repositories, pull requests (list, create, drafts, edit, commits, diff, activity timeline), code review with inline comments on specific diff lines and approve/request-changes/decline/unapprove verdicts, assigning reviewers and labels, and GitVerse Actions CI, listing runs, triggering workflows, and reading jobs and their logs. Tool names and semantics deliberately mirror the popular bitbucket-mcp npm package, so an agent already familiar with it understands the capability set right away.

Who it is for. For GitVerse teams who want to run code review and CI directly from a chat with an agent.

Good fit when

  • You need to leave inline diff comments and set review verdicts on GitVerse
  • You need to trigger and inspect GitVerse Actions CI pipeline logs
  • You already know bitbucket-mcp and want the same tool names for GitVerse

Not a fit when

  • You need to merge a pull request: there is no merge endpoint in GitVerse's public API, so no tool either
  • You need PR tasks or resolving/reopening comment threads: these are also missing from GitVerse's API

Example request

Leave an inline comment on line 25 of src/service.ts in pull request 14 and approve it

Limitations

GitVerse's API caps requests at 2000 per user per hour; the server retries automatically on 429 responses, honoring Retry-After. The public API does not support merging a PR (only checking if it is merged and updating the branch from base), requesting reviewers at PR creation (only assignees), toggling draft status after creation, PR tasks, resolving/reopening comment threads, or cancelling a CI run, so there are no corresponding tools.

How to disable. Remove the gitverse entry from your MCP client config and revoke the personal token in GitVerse settings.

MCP

Transport
stdio
Authentication
API key
Environment variables
GITVERSE_TOKEN
required, secret		GitVerse personal token with rights for repositories, PRs and CI/CD
GITVERSE_BASE_URL
API base, defaults to https://api.gitverse.ru

Security check

  • It can set review verdicts, write and delete comments, and trigger CI pipelines under the token owner's identity
  • The personal token grants repository access under the rights of the user who created it

README in short

The README gives a table of 25 tools across five groups, three install methods (npx, global, project), an environment variable table, token-creation instructions with the needed scopes, config snippets for ZCode, Claude Desktop and Cursor, a 401/429/400 troubleshooting section, and an explicit list of GitVerse's public API limitations.

FAQ

Can this server merge a pull request?

No, GitVerse's public API has no merge endpoint, only a merge-status check and updating the branch from base.

Are the tool names compatible with bitbucket-mcp?

Yes, the 25-tool set deliberately mirrors the names and semantics of the popular bitbucket-mcp package.

Editors’ pick

A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review

PluginMedium riskNo VPN needed292.5K
Editors’ pick

Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture

SkillLow risk271.4K
Editors’ pick

GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation

CLIMedium riskNo VPN needed139.3K

Reference MCP servers

Model Context Protocol servers

Official

Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything

MCP serverMedium risk90.6K
Foxx AIGitVerse MCP: code review and PRs

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.