mcp-gitea
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CF_ID | No | Cloudflare Access client ID (optional, for instances behind Cloudflare Zero Trust). | |
| CF_SECRET | No | Cloudflare Access client secret (optional). | |
| GITEA_TOKEN | Yes | Your Gitea personal access token. | |
| GITEA_API_URL | No | Base URL of the Gitea API (default: https://git.your-instance.com/api/v1). | |
| MCP_ALLOWED_PATHS | No | Comma-separated list of allowed paths for file operations (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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_safe_shellB | Execute a safe shell command (git only) in a specific directory |
| list_reposB | Get a list of all user/organization repositories |
| list_issuesC | Get a list of all open issues in the repository |
| search_issuesC | Search for issues in a repository using keywords |
| get_issue_detailsB | Read the full issue description and its status |
| add_commentB | Leave a comment on a Gitea issue |
| create_issueC | Create a new issue in the repository |
| list_labelsB | Get a list of all labels in the repository |
| list_branchesC | List branches in the repository |
| create_pull_requestC | Create a Pull Request |
| update_issueB | Update an issue (change state, title, body, or labels) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-issue |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct resource and action, with no overlap. For example, 'list_repos', 'list_issues', and 'list_labels' clearly differentiate repositories, issues, and labels. 'search_issues' and 'list_issues' serve different purposes (search vs. listing).
Most tools follow a consistent verb_noun pattern (e.g., 'list_repos', 'create_issue', 'update_issue'). The one exception is 'run_safe_shell', which uses an adjective between verb and noun, breaking the pattern slightly.
With 11 tools, the set is well-scoped for a Gitea MCP server. It covers essential operations like repository listing, issue management (CRUD, search, labels, comments), branch listing, and pull request creation without being excessive.
The tool set covers issue workflows well (create, read, update, comment, search, labels) but misses repository creation/deletion and pull request operations beyond creation (e.g., listing, merging). Branch management is limited to listing, and the 'run_safe_shell' tool is an outlier.