Gitea MCP vs Git
A side-by-side look at the Gitea MCP and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gitea MCP for version control work as a local process; choose Git 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 MCP when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GITEA_URL, GITEA_TOKEN.
Choose Git when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 36/100 · Fair | 81/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | GITEA_URLGITEA_TOKEN | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 2 | 91,487 |
| Directory activity | 1 views 0 installs 0 upvotes | 49 views 0 installs 0 upvotes |
| Tools | Not listed | 16 |
| Full listing | View Gitea MCP | View Git |
Tools & capabilities
Gitea MCP tools
No tool names declared yet. Check the project README from the listing page.
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 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 MCP
{
"mcpServers": {
"gitea-mcp": {
"command": "uvx",
"args": [
"gitea-mcp"
],
"env": {
"GITEA_URL": "YOUR_GITEA_URL_HERE",
"GITEA_TOKEN": "YOUR_GITEA_TOKEN_HERE"
}
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Frequently asked questions
Gitea MCP is categorized under Version Control and uses a local stdio subprocess. Git belongs to Version Control and uses a local stdio subprocess. Pick Gitea MCP for version control work and Git 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 MCP has no declared pricing — check the project's own site. Git is listed as free. Auth: no auth required. 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 gitea-mcp and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gitea MCP has a quality signal of 36/100 (Fair) with 1 views, 0 installs and 2 GitHub stars. Git has 81/100 (Excellent) with 49 views, 0 installs and 91,487 GitHub stars.