Provides comprehensive integration with Gitea API including ~22 intelligent MCP tools for workflow analysis, content generation, and compliance checking, plus 200+ CLI commands for complete CRUD operations on issues, pull requests, repositories, wikis, releases, branches, and CI/CD configuration.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Gitea MCP Tool list open issues in the entai-gitea-mcp repository"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Gitea API 的 MCP (Model Context Protocol) 服务器，让 AI 助手能够与 Gitea 进行交互。
┌─────────────────────────────────────────────────────────────┐
│ Gitea MCP Tool v2.0 │
├─────────────────────────────────────────────────────────────┤
│ │
│ ┌─────────────────┐ ┌─────────────────────────┐ │
│ │ MCP Server │ │ keactl CLI │ │
│ │ (Lite Mode) │ │ (Full Features) │ │
│ ├─────────────────┤ ├─────────────────────────┤ │
│ │ ~22 智能工具 │ │ 200+ 命令 │ │
│ │ • 智能分析 │ │ • 完整 CRUD 操作 │ │
│ │ • 内容生成 │ │ • Issue/PR/Repo 管理 │ │
│ │ • 工作流管理 │ │ • Wiki/Release/Branch │ │
│ │ • 规范检查 │ │ • CI/CD 配置 │ │
│ └────────┬────────┘ └────────────┬────────────┘ │
│ │ │ │
│ └────────────┬───────────────────┘ │
│ ▼ │
│ ┌─────────────────┐ │
│ │ Gitea API │ │
│ └─────────────────┘ │
└─────────────────────────────────────────────────────────────┘Related MCP server: @maxronner/tea-mcp
MCP 智能工具 - ~22 个智能分析、内容生成、工作流管理工具
keactl CLI - 200+ 命令，完整 CRUD 操作（Issue/PR/Repo/Wiki/Release）
低 Context 消耗 - MCP Lite 模式优化，减少 90% token 使用
多客户端支持 - Claude Desktop/CLI、OpenCode、Codex、Cline、Cursor
8 个交互式 Prompts - 引导式操作模板
# npm 安装（推荐）
npm install -g gitea-mcp-tool
# 或使用安装脚本
curl -fsSL https://gitea.ktyun.cc/Kysion/entai-gitea-mcp/raw/branch/main/install-quick.sh | bashClaude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"gitea-mcp-tool": {
"command": "gitea-mcp",
"env": {
"GITEA_BASE_URL": "https://your-gitea-server.com",
"GITEA_API_TOKEN": "your_token_here"
}
}
}
}Claude CLI (~/.claude.json):
{
"mcpServers": {
"gitea-mcp-tool": {
"type": "stdio",
"command": "gitea-mcp",
"env": {
"GITEA_BASE_URL": "https://your-gitea-server.com",
"GITEA_API_TOKEN": "your_token_here"
}
}
}
}OpenCode (~/.config/opencode/config.json):
{
"mcpServers": {
"gitea-mcp-tool": {
"type": "stdio",
"command": "gitea-mcp",
"env": {
"GITEA_BASE_URL": "https://your-gitea-server.com",
"GITEA_API_TOKEN": "your_token_here"
}
}
}
}通用 MCP 配置 (.mcp.json 放在项目根目录):
{
"mcpServers": {
"gitea-mcp-tool": {
"type": "stdio",
"command": "gitea-mcp",
"env": {
"GITEA_BASE_URL": "https://gitea.ktyun.cc",
"GITEA_DEFAULT_OWNER": "Kysion",
"GITEA_DEFAULT_REPO": "entai-gitea-mcp"
}
}
}
}在运行前，请在环境变量中提供
GITEA_API_TOKEN，否则服务器会因缺少认证而启动失败。
登录 Gitea → 设置 → 应用
生成新令牌
复制到配置文件
v2.0 采用 MCP 智能工具 + keactl CLI 混合模式：
操作类型 | 推荐方式 | 示例 |
智能分析 | MCP 工具 |
|
内容生成 | MCP 工具 |
|
CRUD 操作 | keactl CLI |
|
批量操作 | keactl CLI |
|
// 智能标签推断
gitea_workflow_infer_labels({ issue_number: 42, auto_apply: true })
// 规范检查
gitea_compliance_check_all()
// 生成工作流报告
gitea_workflow_generate_report({ time_range: "week" })
// AI 辅助创建 Issue
gitea_issue_create({ title: "Bug: 登录失败", body: "详细描述..." })# 仓库操作
keactl repo list
keactl repo get
# Issue 操作
keactl issue list --state open
keactl issue get 42
keactl issue create --title "Bug" --body "描述"
keactl issue close 42
# PR 操作
keactl pr list
keactl pr create --title "feat: 新功能" --head feature --base main
keactl pr merge 1
# Wiki 操作
keactl wiki list
keactl wiki get "Home"
keactl wiki create --title "Guide" --content "# 指南"
# Release 操作
keactl release list
keactl release create --tag v1.0.0
# Branch 操作
keactl branch list
keactl branch create feature/new
# CI/CD 配置
keactl cicd init
keactl cicd status
keactl cicd validate工具 | 说明 |
| 初始化项目配置 |
| 升级 MCP 工具 |
| 获取当前上下文 |
| 设置默认上下文 |
| 获取当前用户 |
工具 | 说明 |
| AI 辅助创建 Issue |
| AI 辅助创建 PR |
工具 | 说明 |
| 初始化工作流配置 |
| 加载工作流配置 |
| 同步标签系统 |
| 同步项目看板 |
| 检查 Issue 工作流 |
| 智能标签推断 |
| 检测阻塞 Issue |
| 优先级自动升级 |
| 状态双向同步 |
| 生成工作流报告 |
工具 | 说明 |
| 初始化规范配置 |
| 检查分支命名 |
| 检查提交信息 |
| 检查 PR 规范 |
| 全面规范检查 |
多客户端配置指南 - Claude Desktop/CLI、OpenCode、Cline、Cursor、Continue 配置
详细文档请参阅 Wiki:
当前版本: v2.0.0-beta | MCP 工具数: ~22 | CLI 命令数: 200+
MIT License
Run comprehensive compliance check on branch, commits, and/or PR. Returns detailed report.
Inputs: owner, repo, branch, pr_number, +3 more.
Check if branch name complies with naming conventions. Returns compliance status and suggestions.
Inputs: branch (required), config_path.
Check if commit message complies with Conventional Commit format. Can check by SHA or message directly.
Inputs: owner, repo, sha, message, +2 more.
Check if PR description complies with format requirements (sections, issue links, etc.).
Inputs: pr_number (required), owner, repo, config_path, +1 more.
Initialize compliance configuration file (.gitea/compliance.yaml) with default rules.
Inputs: force, config_path.
Get current default context (owner, repo, org, project)
Inputs: no named parameters.
Set default context for subsequent operations. All parameters are optional.
Inputs: owner, repo, org, project.
Initialize project configuration files (.gitea-mcp.json). Auto-detects Git repository info if available.
Inputs: owner, repo, gitea_url, set_as_default, +1 more.
Create a new issue. Use this tool for AI-assisted issue creation with smart content generation.
Inputs: title (required), owner, repo, body, +4 more.
Upgrade Gitea MCP tool to the latest version. Downloads and installs from the latest release.
Inputs: auto_confirm.
Create a new pull request. Use this tool for AI-assisted PR creation with smart content generation.
Inputs: title (required), head (required), base (required), owner, +6 more.
Get information about the currently authenticated user
Inputs: no named parameters.
Detect issues that are blocked or exceeding SLA. Checks for stale issues based on priority-specific time limits.
Inputs: owner, repo, threshold_hours.
Check all open issues against workflow rules. Identifies missing labels, conflicts, and provides suggestions for improvement.
Inputs: owner, repo, issue_number, rules.
Automatically escalate priority for aged issues. P3→P2 after 30 days, P2→P1 after 14 days, P1→P0 after 3 days. Security issues are always P0.
Inputs: owner, repo, dry_run.
Generate a comprehensive workflow report including issue statistics, health score, and recommendations. Output in JSON and Markdown formats.
Inputs: owner, repo, time_range.
Infer labels for an issue based on title and body content. Uses keyword matching and pattern recognition to suggest type, priority, and area labels.
Inputs: issue_number (required), owner, repo, auto_apply.
Initialize Issue workflow configuration for a project. Generates .gitea/issue-workflow.yaml with labels, board columns, and automation rules based on project type.
Inputs: project_type (required), owner, repo, language.
Load and parse the workflow configuration from .gitea/issue-workflow.yaml. Returns the parsed config and validation results.
Inputs: owner, repo.
Create or update project board with columns mapped to status labels. Columns: Backlog, In Progress, Review, Testing, Done.
Inputs: owner, repo, board_name.
Sync repository labels based on workflow configuration. Creates status/, priority/, type/* and other labels defined in the config.
Inputs: owner, repo, dry_run.
Synchronize issue status labels with project board column positions. Supports label-to-board, board-to-label, or bidirectional sync.
Inputs: direction (required), owner, repo.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 22 tools
Most tools have distinct purposes, but there is some overlap in the compliance and workflow categories that could cause confusion. For example, gitea_compliance_check_all and the individual compliance checks (branch, commit, pr) might be ambiguous about when to use each, and the workflow tools like gitea_workflow_check_issues and gitea_workflow_generate_report have overlapping functions in analyzing issues. However, descriptions help clarify boundaries.
Tool names follow a highly consistent pattern with the prefix 'gitea_' followed by a category (e.g., compliance, context, workflow) and a descriptive verb_noun combination. All tools use snake_case uniformly, making them predictable and easy to parse. This consistency aids in understanding the tool set at a glance.
With 22 tools, the count is on the higher side for a server focused on Gitea integration, which might feel heavy and potentially overwhelming. While it covers compliance, context, issues, PRs, and workflow automation, some tools could be consolidated or omitted without losing functionality, indicating borderline appropriateness for the scope.
The tool set provides comprehensive coverage for compliance checks, issue and PR creation, workflow automation, and context management in Gitea. Minor gaps exist, such as missing tools for updating or deleting issues/PRs, and limited operations on repositories beyond compliance (e.g., no list_repos or get_repo). However, agents can work around these with the available tools for core workflows.
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Operate GitHub from your AI assistant: repos, PRs, issues, Actions. Previews and read-only mode.
AI-native git hosting — repos, PRs, issues, CI gates, and AI code review over MCP (60 tools).
Connect AI assistants to your GitHub-hosted Obsidian vault to seamlessly access, search, and analy…
