Gitea vs Github MCP
A side-by-side look at the Gitea and Github 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 Github MCP for version control as a local process. 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 Github MCP when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GITHUB_MCP_ENABLE_WRITE, GITHUB_TOKEN. - You want tools like
get_repo, list_issues, get_issue.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 45/100 · Fair | 49/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | FORGEJO_TOKEN_READ_ONLY | GITHUB_MCP_ENABLE_WRITEGITHUB_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 46 | 14 |
| Full listing | View Gitea | View Github 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
Github MCP tools 14
get_repoRepo metadata (stars, language, license, default branch, archived flag...)list_issuesList issues on a repo (PRs filtered out)get_issueFetch a single issuelist_pull_requestsList pull requests on a repoget_pull_requestFetch a single pull requestget_file_contentRead a repo file's content (base64-decoded, binary detected not decoded)search_reposSearch public repositoriesget_userPublic user/org profilelist_commitsList commits on a branch/refcreate_issueOpen an issuecomment_on_issueComment on an issue/PRupdate_issue_stateOpen/close an issue- +2 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.
Github MCP
{
"mcpServers": {
"github-mcp": {
"command": "uvx",
"args": [
"jaimenbell-github-mcp"
],
"env": {
"GITHUB_MCP_ENABLE_WRITE": "YOUR_GITHUB_MCP_ENABLE_WRITE_HERE",
"GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Gitea is categorized under Version Control and uses an install path we have not confirmed yet. Github MCP belongs to Version Control and uses a local stdio subprocess. Pick Gitea for version control work and Github MCP for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Gitea has no confirmed install command yet — follow its own setup instructions.
Gitea has no declared pricing — check the project's own site. Github 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 github-mcp 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. Github MCP has 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.