- Home
- MCP servers
- Gitea MCP Tool
Gitea MCP Tool
- typescript
1
GitHub Stars
typescript
Language
5 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"supenbysz-gitea-mcp-tool": {
"command": "gitea-mcp",
"args": [],
"env": {
"GITEA_BASE_URL": "https://your-gitea-server.com",
"GITEA_API_TOKEN": "your_token_here",
"GITEA_DEFAULT_REPO": "entai-gitea-mcp",
"GITEA_DEFAULT_OWNER": "Kysion"
}
}
}
}You can use the Gitea MCP Tool to enable an AI assistant to interact with Gitea through a lightweight MCP server. It exposes a set of smart MCP tools and a CLI for full repository, issue, PR, and workflow management, while optimizing context usage for efficient conversations.
How to use
Set up a local MCP server client pair and connect your favorite MCP client to the Gitea MCP Tool. You will run a local MCP server process that talks to Gitea, and then use either smart MCP tools for tasks like smart analysis, content generation, and workflow checks, or the keactl CLI for concrete CRUD operations across issues, PRs, repos, wikis, and releases.
How to install
Prerequisites: Node.js and npm must be installed on your system.
# npm install (global installation recommended)
npm install -g gitea-mcp-tool
# or use the installation script
curl -fsSL https://gitea.ktyun.cc/Kysion/entai-gitea-mcp/raw/branch/main/install-quick.sh | bash
Configuration and usage notes
Configure your MCP client to connect to the Gitea MCP Tool local server. The following configuration examples show the necessary environment variables and how to reference the MCP server from popular clients.
{
"mcpServers": {
"gitea-mcp-tool": {
"type": "stdio",
"command": "gitea-mcp",
"env": {
"GITEA_BASE_URL": "https://your-gitea-server.com",
"GITEA_API_TOKEN": "your_token_here",
"GITEA_DEFAULT_OWNER": "Kysion",
"GITEA_DEFAULT_REPO": "entai-gitea-mcp"
}
}
}
}
Security and tokens
Before starting the MCP server, provide a valid API token for Gitea authentication. The server will fail to start if the token is missing.
Starting and managing the server
Start the local MCP server using your MCP client configuration. If you need to update or upgrade the MCP tool, use the designated upgrade commands available in the toolset.
Additional notes
You can use the MCP tools for infrastructure setup, smart content generation, workflow analysis, and compliance checks. The toolset includes around 22 smart tools for analysis, generation, and workflow management, plus a keactl CLI with over 200 commands for comprehensive repository administration.
Available tools
gitea_init
Initialize project configuration for MCP workflows and environment setup.
gitea_mcp_upgrade
Upgrade MCP tool to the latest compatible version.
gitea_context_get
Fetch the current MCP context and repository scope.
gitea_context_set
Set the default MCP context (owner/repo) for commands.
gitea_user_current
Retrieve the currently authenticated Gitea user.
gitea_issue_create
AI-assisted creation of an Issue with title and body.
gitea_pr_create
AI-assisted creation of a Pull Request.
gitea_workflow_init
Initialize workflow configuration for the repository.
gitea_workflow_load_config
Load workflow configurations from the repository.
gitea_workflow_sync_labels
Synchronize labels with the project workflow.
gitea_workflow_sync_board
Synchronize project board with current issues and PRs.
gitea_workflow_check_issues
Check issues against defined workflow rules.
gitea_workflow_infer_labels
Infer labels automatically based on issue/PR content.
gitea_workflow_check_blocked
Detect issues that are blocked by other tasks.
gitea_workflow_escalate_priority
Automatically escalate priority when needed.
gitea_workflow_sync_status
Synchronize issue/PR status between systems.
gitea_workflow_generate_report
Generate a report of workflow status over a time range.
gitea_compliance_init
Initialize compliance configuration for checking standards.
gitea_compliance_check_branch
Check branch naming against conventions.
gitea_compliance_check_commit
Check commit messages for format and content rules.
gitea_compliance_check_pr
Check PRs for compliance with guidelines.
gitea_compliance_check_all
Perform a comprehensive compliance check across the repository.