Skip to main content
Glama

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_PATHS environment variable.

  • Git Safety: Only whitelisted git subcommands are allowed. Global flags are blocked.

πŸ“¦ Installation

npm install @boringstudio_org/gitea-mcp

πŸš€ Usage

# 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-mcp

Standalone (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.js

As a Library

import { runGiteaServer } from "@boringstudio_org/gitea-mcp";
// Ensure environment variables are set
runGiteaServer().catch(console.error);

πŸ“ License

MIT

Available Tools

11 tools
add_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

    B3.1/5.0

    Scored across 11 tools

    Disambiguation5/5

    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).

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      MCP server for managing Gitea repositories via the Gitea API, enabling operations on issues, comments, labels, milestones, and repository info.
      72
      39 npm
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Forgejo that exposes tools for pull requests, repositories, and issues, leveraging the local fj CLI.
      -