GitHub
by github
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Computer or cloud★ 34,245MITUpdated 3 days ago
Install
GitLab MCP
Overview
Description from the maker (original English)
GitLab over MCP from your own account: issues, merge requests, reviews, the repository and CI.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Developer tools
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account mmedum, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Developer toolsi
- More stars than 0% of the other 1390 servers in this category
- Published to the registry more recently than 94% of the other 1390 servers in this category
- Basic checks equal to or better than 100% of the other 1390 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is GitLab MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (4.3.0) reached the registry 2 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Desktop Commander
by wonderwhy-er
MCP server for terminal commands, file operations, and process management
Runs on your computer★ 10,225MITUpdated 15 days ago
Install
Cloudflare MCP
by cloudflare
Cloudflare MCP servers
Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
gitlab-mcp
An MCP server for gitlab.com. One binary over stdio, signed in as you, with your own OAuth application and the token in your OS keyring.
It is for a person with a gitlab.com account who wants an assistant to find and read issues, review merge requests, follow CI and make the changes they ask for, as them. It works inside projects: issues, merge requests, reviews, the repository and CI. It does not administer an instance or a group, and it does not serve self-managed instances.
Unofficial, and not affiliated with GitLab Inc. See NOTICE.
Goals and non-goals
Goals:
- Content never steers the assistant through the server. Issues, reviews, files and job logs come back marked as untrusted data, hidden text is counted, nothing they link to is fetched, and token shapes in CI output are masked.
- Nothing it writes runs a command. A quick action such as
/mergein a comment is refused or escaped, never executed. - Nothing ships, deletes or reaches further unless you turn it on. Merging, approving, running CI and deleting are not registered by default, code reaches a protected branch only through a merge request, and writes can be confined to the groups you name.
- A write changes only what you read and named. Writes carry what they read and are refused when it moved, a lost create is settled by reading, and every write takes
dry_run. - Reads are bounded. Every read has a budget and says what it left out and how to continue.
- Act as you, and log nothing about your work. Every call runs as the signed-in account, and the logs never carry paths, titles or bodies.
Non-goals:
- Self-managed instances. It talks to gitlab.com and nothing else.
- Administration. Instance and group settings, users, runners, access tokens, deploy keys, webhooks and integrations are out.
- CI variables and secure files. Reading them would put secrets in a model's context.
- Deleting projects or groups, force pushes and protected-branch settings, not even behind a switch.
- A raw API tool. Every call is a tool with its own guards; nothing sends an arbitrary REST or GraphQL request.
- Events pushed to it. Webhooks need a listener, and a stdio process has none.
- A hosted service. It speaks stdio only, so Claude on the web and on mobile cannot reach it.
- Asking you before a call. Your client approves each call; the server asks nothing.
What makes this one different
- A curated surface, gated by registration. A tool for each thing a person does in a project, rather than an API mirror, and a tool that is switched off is not registered, so it cannot be called at all.
- Nothing it writes runs a quick action. GitLab runs
/mergeand the rest from any comment or description sent through its API. - Content is marked as untrusted. Issues, reviews, files and job logs come back inside boundaries the content cannot close.
- Reviews the way people review. Draft comments, published together, and the server, not the model, computes where an inline comment lands.
- Signs in like a desktop app. Your own OAuth application, a browser tab, the token in the OS keyring. GitLab's own MCP server runs on the instance over HTTP, and a stdio client reaches it through a Node.js proxy.
- Verifiable releases. Signed checksums, build provenance and SBOMs.
Tools
| Tool | What it does |
|---|---|
get_me | Who is signed in, with which scopes, and what GitLab reports about itself |
resolve_url | Turn a GitLab web URL into the arguments another tool takes, and name that tool |
search_projects | Find projects by name, or within a group |
get_project | One project: default branch, visibility, what it has turned on |
list_members | Who has access to a project, and with which role |
find_users | Accounts by exact username or by name |
search_issues | Find issues across gitlab.com, a group or a project |
get_issue | One issue, its description marked as untrusted content, and its linked merge requests |
create_issue | Create an issue; labels, assignees and milestone checked first |
update_issue | Change an issue's fields, refused if it changed since you read it |
list_discussions | The comment threads on an issue or a merge request |
list_item_events | An issue's or a merge request's label, state, milestone and weight changes, newest first |
add_comment | Comment on an issue or merge request, reply in a thread, or start one, on a diff line or not |
update_comment | Edit one of your own comments in place, in its thread and on its diff line |
resolve_discussion | Resolve or reopen a thread on a merge request or an issue |
link_issues | Link two issues, in one project or two |
unlink_issues | Remove the link between two issues |
link_merge_requests | Make one merge request wait for another to merge, in one project or two |
unlink_merge_requests | Remove a dependency between two merge requests |
search_merge_requests | Find merge requests across gitlab.com or a project |
get_merge_request | One merge request with its approvals, reviewer states, linked issues and dependencies |
list_mr_files | The files a merge request changes, with line counts and GitLab's markers |
get_mr_diff | A merge request's diffs, file by file, bounded |
list_mr_commits | A merge request's commits |
list_mr_versions | A merge request's diff versions, one per push |
compare_mr_versions | What changed between two versions of a merge request, or since one |
create_merge_request | Open a merge request from a branch |
update_merge_request | Change a merge request's fields, refused if it changed since you read it |
track_time | Set or reset an issue's or a merge request's time estimate, and add or reset its time spent |
add_review_comment | A draft review comment, on the merge request or a diff line |
list_review_comments | Your unpublished review comments on a merge request |
delete_review_comment | Delete one of your drafts |
update_review_comment | Change the text of one of your drafts, keeping its place |
publish_review_comment | Publish one of your drafts on its own |
submit_review | Publish all your drafts at once, with a summary and reviewer state |
rerequest_review | Ask a reviewer for a new review once their requested changes are addressed |
get_file | A file at a ref, bounded |
list_tree | A directory listing at a ref |
list_branches | A project's branches |
list_commits | Commits on a ref or a path |
get_commit | One commit and its diff, bounded, and the merge requests that contain it |
compare_refs | The commits and diffs between two refs, bounded |
list_tags | A project's tags |
create_branch | Create a branch from a ref |
create_commit | Commit file changes to a branch; never the default or a protected one |
get_blame | Who last changed each line of a file, bounded |
cherry_pick_commit | Apply a commit to a branch; never the default or a protected one |
revert_commit | Undo a commit on a branch with a new one; never the default or a protected one |
list_pipelines | A project's CI pipelines |
get_pipeline | One pipeline with the jobs that failed, trigger jobs included |
list_jobs | A pipeline's jobs |
get_job_log | A window of a job's log, secrets masked; the failing section on request |
get_test_report | A pipeline's test counts and failed cases, secrets masked, bounded |
lint_ci | Check a project's CI configuration at a ref, or configuration you pass |
list_job_artifacts | The files a job kept as artifacts |
get_job_artifact | One text file of a job's artifacts, secrets masked, bounded |
list_labels | The labels a project's issues and merge requests can carry |
list_milestones | A project's or a group's milestones |
list_boards | A project's issue boards and their lists, each with the search_issues arguments that read it |
search | Code, commits, comments and more, in a project, a group or everywhere |
| delete_label | Delete a project label (`
Only the beginning is shown; read the rest in the repo