MCP.Market

gitea-mcp server

by werebear73·io.github.werebear73/gitea-mcp·v0.5.1
No reviews yet

Model Context Protocol server for Gitea (and Forgejo, Codeberg).

B72/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B72/100

full report

Adoption
New

0 stars115 downloads/wk

Reviews

Write one

Nobody has reviewed gitea-mcp yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

gitea-mcp tools (24, 6 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • add_comment

    Add a comment to an existing issue. Returns the created Comment object.

  • add_comment_on_pr

    Add a comment to a pull request's discussion thread.

  • build_parser

    argparse parser for the ``doctor`` subcommand.

  • commit_changeswrite action

    Create or update a single file on a branch in one commit.

  • create_branchwrite action

    Create a new branch in a repository.

  • create_issuewrite action

    Create a new issue in a Gitea repository.

  • create_prwrite action

    Open a new pull request from ``head`` into ``base``.

  • get_client

    Return the singleton :class:`GiteaClient`.

  • get_issue

    Get a single issue by number, including all of its comments.

  • get_pull_request

    Get a single pull request by number, including its discussion comments.

  • get_server_info

    Return information about the running gitea-mcp server and its Gitea connection.

  • get_server_version

    Return the running gitea-mcp server's version.

  • list_branches

    List branches in a repository.

  • list_issues

    List issues in a Gitea repository.

  • list_labels

    List labels defined in a repository.

  • list_milestones

    List milestones in a repository, optionally filtered by state.

  • list_pull_requests

    List pull requests in a repository, optionally filtered by state.

  • list_releases

    List releases for a repository.

  • list_repos

    List repositories.

  • main

    Console-script entry point.

  • merge_pr

    Merge a pull request.

  • read_file

    Read a file's content from a Gitea repository.

  • runwrite action

    Execute the serve flow. Returns a process exit code.

  • update_issuewrite action

    Update an existing issue's title, body, state, assignees, milestone, or labels.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan20 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 121 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 72/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How gitea-mcp compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
72/100
higher than 40% of 4,460 AI and agents servers
Tools
24
the typical AI and agents server has 6
Tools that change things
25%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
115
more than 66% of 1,538 AI and agents servers with a package

What its tools let an agent do: 15 read · 5 create · 3 change · 1 run or deploy

Install gitea-mcp in Claude Code, Cursor or VS Code

claude mcp add gitea-mcp -- uvx gitea-mcp
Add to Cursor

What the publisher says

From the gitea-mcp repository's README, as published. We do not edit it. Read it on GitHub

gitea-mcp

<!-- mcp-name: io.github.werebear73/gitea-mcp -->

A Model Context Protocol server for Gitea — lets AI assistants (Claude, ChatGPT, Copilot, and anything else that speaks MCP) read, create, and manage issues, repositories, and releases on any Gitea instance you can reach.

Also works against Forgejo and Codeberg (API-compatible).

Why

Self-hosted Gitea is a popular GitHub alternative for solo developers, small teams, and privacy-conscious organizations. With this MCP server installed, your AI assistant can:

  • File audit findings or refactor notes as Gitea issues without you leaving the chat
  • Triage a repo's open issues in natural language
  • Cut a release at the end of a coding session
  • Comment on issues across multiple repos in one pass

Features

  • Bearer authentication via Personal Access Token (PAT)
  • Async HTTP via httpx and FastMCP
  • Works with self-hosted Gitea, Forgejo, and Codeberg

Quick Start

1. Install

pip install gitea-mcp

Or with uv:

uv pip install gitea-mcp

2. Generate a Personal Access Token

In your Gitea instance, go to Settings → Applications → Generate New Token and grant at least:

  • read:repository
  • write:issue
  • read:user

Add write:repository if you also want to create releases.

3. Configure your MCP client

Claude Desktop (interactive): run

gitea-mcp init

It prompts for the Gitea URL and Personal Access Token, verifies the connection, and writes (or merges into) the right claudedesktopconfig.json for your OS. Restart Claude Desktop and you're done.

To check that the server can reach your Gitea instance at any time:

gitea-mcp doctor

doctor reads GITEAURL and GITEATOKEN from the environment, runs a GET /api/v1/user, and reports the authenticated username plus the state of the MCP tool surface. Exit 0 = ready; exit 1 = connection/load failure; exit 2 = missing config.

Any MCP client (manual): add gitea-mcp to the client's MCP config. The recommended form uses uvx so the client launches the latest published wheel in an isolated env without needing gitea-mcp on its own PATH (this is what gitea-mcp init writes):

{
  "mcpServers": {
    "gitea": {
      "command": "uvx",
      "args": ["gitea-mcp"],
      "env": {
        "GITEA_URL": "https://your-gitea-instance.example.com",
        "GITEA_TOKEN": "your-personal-access-token"
      }
    }
  }
}

If you'd rather use a globally pip-installed gitea-mcp binary, drop args and set command to "gitea-mcp" directly — works as long as the binary is on the MCP client's PATH at launch time.

See mcp.json for a complete example. The same shape works for Claude Desktop, VS Code, Cowork, Claude Code, and any other MCP-compatible client.

Configuration

Configuration is read from environment variables.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

gitea-mcp: common questions

Is gitea-mcp server safe?
Mostly: it is graded B (72/100). Read the gitea-mcp safety report
How do I install gitea-mcp?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does gitea-mcp need an API key?
Yes. The registry entry asks for GITEA_TOKEN.
Is gitea-mcp maintained?
The last commit was 158 days ago (2026-05-29). The latest release is v0.5.1.
How does gitea-mcp compare with other AI and agents MCP servers?
safety score 72/100 (higher than 40% of 4,460 AI and agents servers); tools 24 (the typical AI and agents server has 6); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.