Gitea vs Gitlab MCP
A side-by-side look at the Gitea and Gitlab MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gitea for version control work; choose Gitlab MCP for version control. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Gitea when
- You need dedicated capabilities in the Version Control domain.
- You have the keys it needs:
FORGEJO_TOKEN_READ_ONLY. - You want tools like
whoami, version, list_my_repos.
Choose Gitlab MCP when
- You need dedicated capabilities in the Version Control domain.
- You want tools like
get_me, resolve_url, search_projects.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 45/100 · Fair | 45/100 · Fair |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | FORGEJO_TOKEN_READ_ONLY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 46 | 80 |
| Full listing | View Gitea | View Gitlab MCP |
Tools & capabilities
Gitea tools 46
whoamiThe authenticated user (verifies the token)versionThis MCP server's version, the connected instance's version, and its `flavor` (`forgejo` or `gitea`)list_my_reposYour repositories (auto-paginated, slimmed)list_issuesIssues in `owner/repo` (open by default)list_pull_requestsPull requests in `owner/repo` (open by default)get_repoOne repository's details (incl. default branch, size in KiB, and the `has_*` unit toggles), slimmedlist_branchesBranches in `owner/repo` (auto-paginated, slimmed to name/commit/protected)list_commitsCommits on a ref (`owner/repo`, optional `sha` and `path`; auto-paginated). Slimmed to sha, subject, author, date and signature state — the raw objects carry base64 `signature`/`payload` blobs and per-commit `files`/`statsget_commitOne commit (`owner/repo/sha`), same fields. `signature` is `verified`, `unverified` or `unsigned`; `signer` on the first, `reason` on the secondlist_keysAn account's SSH and GPG keys (omit `username` for yourself). `verified` decides whether a signature can verify at all — but **Gitea omits the field on SSH keys**, so absent means unreported, not unverified. GPG entries carry the addresses the key covers and whether each is activatedlist_branch_protectionsA repository's protection rules: what each enforces (`require_signed_commits`, direct pushes, approvals, status checks) for a branch name or glob. Allowlists omitted; an empty list means nothing is protectedget_commit_statusesIndividual statuses against a commit/branch/tag: context, status, description, `target_url`. `get_combined_status` rolls these into one verdict- +34 more on the listing page
Gitlab MCP tools 80
get_meWho is signed in, with which scopes, and what GitLab reports about itselfresolve_urlTurn a GitLab web URL into the arguments another tool takes, and name that toolsearch_projectsFind projects by name, or within a groupget_projectOne project: default branch, visibility, what it has turned onlist_membersWho has access to a project, and with which rolefind_usersAccounts by exact username or by namesearch_issuesFind issues across gitlab.com, a group or a projectget_issueOne issue, its description marked as untrusted content, and its linked merge requestscreate_issueCreate an issue; labels, assignees and milestone checked firstupdate_issueChange an issue's fields, refused if it changed since you read itlist_discussionsThe comment threads on an issue or a merge requestlist_item_eventsAn issue's or a merge request's label, state, milestone and weight changes, newest first- +68 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Gitea
No confirmed install command for Gitea yet — follow the setup steps linked from its listing page rather than a guessed package name.
Gitlab MCP
No confirmed install command for Gitlab MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Gitea is categorized under Version Control and uses an install path we have not confirmed yet. Gitlab MCP belongs to Version Control and uses an install path we have not confirmed yet. Pick Gitea for version control work and Gitlab MCP for version control.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
Gitea has no declared pricing — check the project's own site. Gitlab MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add forgejo-codeberg-gitea and gitlab-mcp-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gitea has a quality signal of 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Gitlab MCP has 45/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.