mcp-gitea
Provides tools for interacting with Gitea, enabling AI agents to manage issues, repositories, files, pull requests, and perform analysis with AI prompts.
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., "@mcp-gitea show open issues for my-org/my-repo"
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 MCP Server
A Model Context Protocol (MCP) server for interacting with Gitea. This package is designed to be used as a standalone server or imported by a gateway.
π Capabilities
Issues: List, search, create, update, comment.
Repositories: List repos, branches, labels.
Files: Read file content.
Pull Requests: Create PRs.
Analysis: Analyze issues with AI prompts.
Shell: Execute safe git commands in WSL (
run_safe_shell).
Related MCP server: gitea-mcp
π Security
Allowed Paths: Restricted via
MCP_ALLOWED_PATHSenvironment variable.Git Safety: Only whitelisted git subcommands are allowed. Global flags are blocked.
π¦ Installation
npm install @boringstudio_org/gitea-mcpπ Usage
Via NPX (Recommended)
# Configure environment variables
export GITEA_TOKEN=your_token
# Optional: Defaults to https://git.your-instance.com/api/v1
export GITEA_API_URL=https://git.your-instance.com/api/v1
# Cloudflare Access (Optional)
# If your Gitea instance is behind Cloudflare Zero Trust
export CF_ID=your_cf_client_id
export CF_SECRET=your_cf_client_secret
# Run
npx @boringstudio_org/gitea-mcpStandalone (From Source)
# Install dependencies
npm install
# Configure .env
echo "GITEA_TOKEN=..." > .env
echo "GITEA_API_URL=..." >> .env
# Optional: Cloudflare Access
echo "CF_ID=..." >> .env
echo "CF_SECRET=..." >> .env
# Run
node index.jsAs a Library
import { runGiteaServer } from "@boringstudio_org/gitea-mcp";
// Ensure environment variables are set
runGiteaServer().catch(console.error);π License
MIT
Available Tools
11 toolsadd_commentB
Leave a comment on a Gitea issue
Inputs: body (required), repo (required), owner (required), issue_number (required).
create_issueC
Create a new issue in the repository
Inputs: repo (required), owner (required), title (required), body.
create_pull_requestC
Create a Pull Request
Inputs: head (required), repo (required), owner (required), title (required), +2 more.
get_issue_detailsB
Read the full issue description and its status
Inputs: repo (required), owner (required), issue_number (required).
list_branchesC
List branches in the repository
Inputs: repo (required), owner (required).
list_issuesC
Get a list of all open issues in the repository
Inputs: repo (required), owner (required), page, limit.
list_labelsB
Get a list of all labels in the repository
Inputs: repo (required), owner (required).
list_reposB
Get a list of all user/organization repositories
Inputs: org.
run_safe_shellB
Execute a safe shell command (git only) in a specific directory
Inputs: cwd (required), args (required), command (required).
search_issuesC
Search for issues in a repository using keywords
Inputs: repo (required), owner (required), query (required), state.
update_issueB
Update an issue (change state, title, body, or labels)
Inputs: repo (required), owner (required), issue_number (required), body, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
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.
Related MCP Connectors
MCP server for siGit (sigit.si): browse repos, search code, manage PRs/issues, web search.
A MCP server built for developers enabling Git based project management with project and personalβ¦
Create, deploy, and operate MCP servers directly from your GitHub repositories.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for managing your repositories on Forgejo/Gitea server.70Mozilla Public 2.0
- AlicenseAqualityBmaintenanceMCP server for managing Gitea repositories via the Gitea API, enabling operations on issues, comments, labels, milestones, and repository info.7239 npm2MIT
- AlicenseNot gradedqualityDmaintenanceA secure, git-aware MCP server for working with local repositories, enabling file management, shell commands, and full git operations within allowed directories.1GPL 3.0
- FlicenseNot gradedqualityDmaintenanceMCP server for Forgejo that exposes tools for pull requests, repositories, and issues, leveraging the local fj CLI.-