gitea-mcp

Name: gitea-mcp
Author: werebear73

作者：werebear73版本 0.5.1i★ –i在你的电脑上运行

注册名称io.github.werebear73/gitea-mcp

安装

概览

作者提供的说明（英文原文）

Model Context Protocol server for Gitea (and Forgejo, Codeberg).

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新↓ 134/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：GITEA_URL, GITEA_TOKEN

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： GITEA_URL, GITEA_TOKEN, GITEA_TIMEOUT, GITEA_MAX_RETRIES, GITEA_RETRY_BASE_DELAY

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "gitea": {
      "command": "uvx",
      "args": [
        "gitea-mcp"
      ],
      "env": {
        "GITEA_URL": "your-value",
        "GITEA_TOKEN": "your-value",
        "GITEA_TIMEOUT": "your-value",
        "GITEA_MAX_RETRIES": "your-value",
        "GITEA_RETRY_BASE_DELAY": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add gitea --env GITEA_URL=your-value --env GITEA_TOKEN=your-value --env GITEA_TIMEOUT=your-value --env GITEA_MAX_RETRIES=your-value --env GITEA_RETRY_BASE_DELAY=your-value -- uvx gitea-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "gitea": {
      "command": "uvx",
      "args": [
        "gitea-mcp"
      ],
      "env": {
        "GITEA_URL": "your-value",
        "GITEA_TOKEN": "your-value",
        "GITEA_TIMEOUT": "your-value",
        "GITEA_MAX_RETRIES": "your-value",
        "GITEA_RETRY_BASE_DELAY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "gitea": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "gitea-mcp"
      ],
      "env": {
        "GITEA_URL": "your-value",
        "GITEA_TOKEN": "your-value",
        "GITEA_TIMEOUT": "your-value",
        "GITEA_MAX_RETRIES": "your-value",
        "GITEA_RETRY_BASE_DELAY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

GITEA_URL 必填 env
Base URL of your Gitea/Forgejo/Codeberg instance
GITEA_TOKEN 机密必填 env
Personal access token for the configured instance
GITEA_TIMEOUT env
HTTP request timeout in seconds
GITEA_MAX_RETRIES env
Retry count for transient failures
GITEA_RETRY_BASE_DELAY env
Retry backoff base delay in seconds

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 werebear73 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 18665 个服务器的 0%
发布到注册中心的时间比此分类中其他 18665 个服务器的 9% 更新
基础检查结果等于或优于此分类中其他 18665 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

gitea-mcp 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：GITEA_URL, GITEA_TOKEN

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.5.1）于5个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Systemdox

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

作者：formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

安装

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

作者：desktop-commander正在增长★ 2114天前更新

在云端运行✓ desktopcommander.app

安装

Systemdox

Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.

作者：puglieseweb正在增长↓ 3028/周今天更新

在你的电脑上运行

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

gitea-mcp

A Model Context Protocol server for Gitea — lets AI assistants (Claude, ChatGPT, Copilot, and anything else that speaks MCP) read, create, and manage issues, repositories, and releases on any Gitea instance you can reach.

Also works against [Forgejo](https://forgejo.org) and [Codeberg](https://codeberg.org) (API-compatible).

Why

Self-hosted Gitea is a popular GitHub alternative for solo developers, small teams, and privacy-conscious organizations. With this MCP server installed, your AI assistant can:

File audit findings or refactor notes as Gitea issues without you leaving the chat
Triage a repo's open issues in natural language
Cut a release at the end of a coding session
Comment on issues across multiple repos in one pass

Features

Resource	Tools
Issues	`create_issue`, `list_issues`, `get_issue`, `update_issue`, `add_comment`
Repos	`list_repos`, `list_labels`, `list_milestones`, `list_branches`
Pulls	`list_pull_requests`, `get_pull_request`, `add_comment_on_pr`, `create_pr`, `merge_pr`
Files	`read_file`, `commit_changes`, `create_branch`
Releases	`list_releases`, `create_release`
Meta	`get_server_info`, `get_server_version`

Bearer authentication via Personal Access Token (PAT)
Async HTTP via httpx and FastMCP
Works with self-hosted Gitea, Forgejo, and Codeberg

Quick Start

1. Install

pip install gitea-mcp

Or with uv:

uv pip install gitea-mcp

2. Generate a Personal Access Token

In your Gitea instance, go to Settings → Applications → Generate New Token and grant at least:

read:repository
write:issue
read:user

Add write:repository if you also want to create releases.

3. Configure your MCP client

Claude Desktop (interactive): run

gitea-mcp init

It prompts for the Gitea URL and Personal Access Token, verifies the connection, and writes (or merges into) the right claude_desktop_config.json for your OS. Restart Claude Desktop and you're done.

To check that the server can reach your Gitea instance at any time:

gitea-mcp doctor

doctor reads GITEA_URL and GITEA_TOKEN from the environment, runs a GET /api/v1/user, and reports the authenticated username plus the state of the MCP tool surface. Exit 0 = ready; exit 1 = connection/load failure; exit 2 = missing config.

Any MCP client (manual): add gitea-mcp to the client's MCP config. The recommended form uses uvx so the client launches the latest published wheel in an isolated env without needing gitea-mcp on its own PATH (this is what gitea-mcp init writes):

"mcpServers": { "gitea": { "command": "uvx", "args": ["gitea-mcp"], "env": { "GITEA_URL": "https://your-gitea-instance.example.com", "GITEA_TOKEN": "your-personal-access-token" } } } }

If you'd rather use a globally pip-installed gitea-mcp binary, drop args and set command to "gitea-mcp" directly — works as long as the binary is on the MCP client's PATH at launch time.

See mcp.json for a complete example. The same shape works for Claude Desktop, VS Code, Cowork, Claude Code, and any other MCP-compatible client.

Configuration

Configuration is read from environment variables.

Variable	Required	Default	Description
`GITEA_URL`	Yes	—	Base URL of your Gitea instance (e.g., `https://gitea.example.com`)
`GITEA_TOKEN`	Yes	—	Personal Access Token from your Gitea user settings
`GITEA_TIMEOUT`	No	`30`	HTTP request timeout in seconds
`GITEA_MAX_RETRIES`	No	`3`	Max retries for transient failures on idempotent methods (`GET`/`PUT`/`DELETE`). Set to `0` to disable retries. `POST` and `PATCH` are never auto-retried — they could create duplicate issues, comments, or releases. `429 Too Many Requests` is retried for any method, honoring `Retry-After` when present.
`GITEA_RETRY_BASE_DELAY`	No	`0.5`	Base delay (seconds) for exponential backoff between retries. Effective delay grows as `base * 2^attempt` with jitter, capped at 4 seconds.

Self-hosting / HTTP transport

By default gitea-mcp runs in stdio mode — each MCP client (Claude Desktop, Cowork, etc.) launches its own subprocess on demand. For self-hosting one instance that multiple clients connect to over the network, use the streamable-HTTP transport:

gitea-mcp serve --transport http --host 0.0.0.0 --port 8000 --path /mcp

All four flags can also be provided via environment variables (handy for Docker / systemd units):

Variable	Default	Flag
`GITEA_MCP_TRANSPORT`	`stdio`	`--transport`
`GITEA_MCP_HOST`	`127.0.0.1`	`--host`
`GITEA_MCP_PORT`	`8000`	`--port`
`GITEA_MCP_PATH`	`/mcp`	`--path`

MCP clients connect to the resulting URL (e.g. https://gitea-mcp.example.com/mcp) just like they would to a local stdio server, except they share the one running instance.

Auth model (this release). The server reads GITEA_TOKEN from its own environment, so any client that reaches the URL acts as that one Gitea user. Run it for yourself behind your own access controls (firewall, reverse-proxy auth, VPN, Tailscale). Multi-tenant bring-your-own-token is on the roadmap.

The no-args invocation (gitea-mcp with no subcommand) still runs in stdio mode, so existing Claude Desktop / Cowork / Claude Code integrations are unaffected by this addition.

Compatibility

Server	Status
Gitea (self-hosted)	✅ Primary target
Forgejo	✅ Expected to work (API-compatible)
Codeberg	✅ Expected to work (Codeberg runs Forgejo)

Development

git clone https://github.com/werebear73/gitea-mcp.git

cd gitea-mcp pip install -e ".[dev]" pre-commit install # commit-stage hooks (ruff + mypy) pre-commit install --hook-type pre-push # push-stage hooks (pytest + build check) pytest

The two-stage pre-commit policy keeps the commit loop snappy (lint + type only) while making git push block on the slow stuff that's actually caught CI/release bugs in the past — the full test suite and python -m build && twine check dist/*, which surfaces setuptools_scm version surprises before they reach a tag push.

Roadmap

See docs/ROADMAP.md for what's shipped, what's next, and what's out of scope.

Publishing

MCP Registry metadata is tracked in server.json.
Smithery + MCP Registry publication steps are documented in docs/PUBLISHING.md.

Versioning

Semantic versioning, derived from git tags via setuptools_scm. See VERSIONING.md for the release process.

Contributing

Issues and pull requests welcome. For substantial changes, please open an issue first to discuss the approach.

License

MIT — use it however you like, including commercial products.

Built by Waretech Services.

gitea-mcp

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

Systemdox

作者的 README

gitea-mcp

Why

Features

Quick Start

1. Install

2. Generate a Personal Access Token

3. Configure your MCP client

Configuration

Self-hosting / HTTP transport

Compatibility

Development

Roadmap

Publishing

Versioning

Contributing

License