Gitea MCP Tool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITEA_BASE_URL | Yes | The base URL of your Gitea server | |
| GITEA_API_TOKEN | Yes | Your Gitea API token for authentication | |
| GITEA_DEFAULT_REPO | No | Default repository name (optional) | |
| GITEA_DEFAULT_OWNER | No | Default owner/organization name (optional) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gitea_initC | Initialize project configuration files (.gitea-mcp.json). Auto-detects Git repository info if available. |
| gitea_mcp_upgradeB | Upgrade Gitea MCP tool to the latest version. Downloads and installs from the latest release. |
| gitea_context_getB | Get current default context (owner, repo, org, project) |
| gitea_context_setC | Set default context for subsequent operations. All parameters are optional. |
| gitea_user_currentB | Get information about the currently authenticated user |
| gitea_issue_createB | Create a new issue. Use this tool for AI-assisted issue creation with smart content generation. |
| gitea_pr_createC | Create a new pull request. Use this tool for AI-assisted PR creation with smart content generation. |
| gitea_workflow_initA | Initialize Issue workflow configuration for a project. Generates .gitea/issue-workflow.yaml with labels, board columns, and automation rules based on project type. |
| gitea_workflow_load_configB | Load and parse the workflow configuration from .gitea/issue-workflow.yaml. Returns the parsed config and validation results. |
| gitea_workflow_sync_labelsC | Sync repository labels based on workflow configuration. Creates status/, priority/, type/* and other labels defined in the config. |
| gitea_workflow_sync_boardC | Create or update project board with columns mapped to status labels. Columns: Backlog, In Progress, Review, Testing, Done. |
| gitea_workflow_check_issuesC | Check all open issues against workflow rules. Identifies missing labels, conflicts, and provides suggestions for improvement. |
| gitea_workflow_infer_labelsC | Infer labels for an issue based on title and body content. Uses keyword matching and pattern recognition to suggest type, priority, and area labels. |
| gitea_workflow_check_blockedB | Detect issues that are blocked or exceeding SLA. Checks for stale issues based on priority-specific time limits. |
| gitea_workflow_escalate_priorityA | 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. |
| gitea_workflow_sync_statusA | Synchronize issue status labels with project board column positions. Supports label-to-board, board-to-label, or bidirectional sync. |
| gitea_workflow_generate_reportB | Generate a comprehensive workflow report including issue statistics, health score, and recommendations. Output in JSON and Markdown formats. |
| gitea_compliance_check_branchB | Check if branch name complies with naming conventions. Returns compliance status and suggestions. |
| gitea_compliance_check_commitB | Check if commit message complies with Conventional Commit format. Can check by SHA or message directly. |
| gitea_compliance_check_prC | Check if PR description complies with format requirements (sections, issue links, etc.). |
| gitea_compliance_check_allB | Run comprehensive compliance check on branch, commits, and/or PR. Returns detailed report. |
| gitea_compliance_initC | Initialize compliance configuration file (.gitea/compliance.yaml) with default rules. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| 配置连接 | 交互式配置 Gitea MCP 服务器连接信息（首次使用必需） |
| 创建Issue | 交互式创建 Gitea Issue 的提示模板 |
| 创建PR | 交互式创建 Gitea Pull Request 的提示模板 |
| 初始化工作流 | 交互式初始化项目 Issue 工作流配置，包含标签系统、项目看板和自动化规则 |
| 管理工作流 | 工作流日常管理面板，支持同步标签、看板、检查配置一致性 |
| Issue巡检 | 智能 Issue 健康检查，识别问题并提供修复建议 |
| 生成工作流报告 | 生成项目 Issue 工作流分析报告，包含统计数据和改进建议 |
| 配置多项目工作流 | 批量为多个项目配置工作流，适用于组织级别的统一管理（使用 keactl CLI） |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.