GitVerse MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITVERSE_TOKEN | Yes | Персональный токен GitVerse | |
| GITVERSE_BASE_URL | No | База API. По умолчанию https://api.gitverse.ru | https://api.gitverse.ru |
| GITVERSE_API_VERSION | No | Версия вендорного media type. По умолчанию 1 | 1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listRepositoriesA | List repositories. Without arguments lists the authenticated user's repositories; pass org to list organization repositories. Supports page/per_page. |
| getRepositoryA | Get details of a specific repository. |
| getPullRequestsC | List pull requests of a repository. state filters by open/closed. Supports page/per_page. |
| createPullRequestA | Create a pull request from head to base. GitVerse has no reviewer requests — use assignees instead. Pass draft=true to create a draft. |
| getPullRequestB | Get details of a specific pull request. |
| updatePullRequestA | 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. |
| getPullRequestActivityA | Get the activity/timeline of a pull request. |
| approvePullRequestC | Approve a pull request by submitting an APPROVED review. |
| unapprovePullRequestA | Remove your approval: finds your latest APPROVED review on the pull request and deletes it. |
| declinePullRequestA | Decline (close) a pull request. An optional message is posted to the discussion before closing. |
| requestChangesA | Request changes on a pull request by submitting a REQUEST_CHANGES review. |
| removeChangeRequestA | Remove your change request by superseding it with an APPROVED review (GitVerse has no dedicated un-request endpoint). |
| createDraftPullRequestA | Create a draft pull request (equivalent to createPullRequest with draft=true). |
| getPullRequestCommentsB | List discussion comments on a pull request. Supports since/before filters. |
| addPullRequestCommentA | Comment on a pull request. Without inline — a general discussion comment. With inline {path, to} — an inline review comment on line |
| updatePullRequestCommentB | Edit a discussion comment on a pull request. |
| deletePullRequestCommentB | Delete a discussion comment on a pull request. |
| getPullRequestDiffA | Get the changed files of a pull request, including per-file patches. |
| getPullRequestCommitsA | List the commits of a pull request. Supports page/per_page. |
| listPipelineRunsA | List CI runs (GitVerse Actions, Bitbucket Pipelines analog). Filters: status, branch, event. Supports page/per_page. |
| getPipelineRunC | Get details of a CI run. |
| runPipelineB | Trigger a CI run of a workflow on a branch or tag. |
| getPipelineStepsB | List jobs (steps) of a CI run. |
| getPipelineStepC | Get details of a CI job (step). |
| getPipelineStepLogsB | Get logs of a CI job (step). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 25 tools
The PR-related tools are numerous but each has a distinct purpose (create, get, list, update, approve, decline, request changes, comments, diff, commits, activity). However, createDraftPullRequest overlaps with createPullRequest (which has a draft parameter), and unapprovePullRequest vs removeChangeRequest could be confused, though descriptions clarify. Overall, an agent can typically select the right tool.
All tool names follow a consistent camelCase verb_noun pattern (listRepositories, getRepository, createPullRequest, getPullRequestDiff, etc.). No mixed conventions or vague verbs like 'process' or 'run' without context.
At 25 tools, this is at the upper edge of acceptable. The large number is driven by PR sub-operations (comments, approvals, changes) and pipeline steps/logs, but the redundant createDraftPullRequest and the tight PR focus make it feel slightly heavy for the scope. Still, each tool addresses a specific need.
Major gaps exist: there is no merge_pull_request tool, no branch/tag management, and no repository-level lifecycle operations beyond list/get. The PR workflow covers review and comments but lacks merging, which is a core operation. Pipeline tools are comprehensive but the overall domain feels incomplete for a full Git hosting server.