Gitea

Gitea

This connector works with Gitea through the REST API v1 (<your Gitea address>/api/v1): repositories, issues with comments, labels and milestones, pull requests with their files, diffs, commits and reviews, releases, organizations with members and teams, branches, commits, the file tree and file contents. It runs against gitea.com or your own Gitea server, as the user who owns the token: the AI sees exactly what that user can see. It is read-only, nothing here creates, changes or deletes anything.

Setup (about 2 minutes)

1. In Gitea click your avatar, then Settings, then Applications. Under Manage Access Tokens type a name (for example "AnythingMCP") and set Repository, Issue, Organization and User to Read (the scopes read:repository, read:issue, read:organization and read:user). A Gitea version without token scopes gives the token the full access of its user.
2. Click Generate Token and copy the token right away, Gitea shows it only once. Paste only the token into GITEA_TOKEN: the adapter sends it as Authorization: token <token> and adds the word token itself.
3. Set GITEA_URL to the address you open Gitea at, for example https://gitea.com or https://git.example.com, without /api/v1 and without a trailing slash. If Gitea runs under a sub path, keep it (https://example.com/gitea).

Your own server: a Gitea on an internal host (a private IP or an internal name) needs a self-hosted AnythingMCP on the same network, with the hostname in SSRF_ALLOWED_HOSTS, or the outbound guard blocks the call. Forgejo, and Codeberg which runs it, offer the same API v1 routes, so an address such as https://codeberg.org should work too; this adapter is written against the Gitea API.

Repositories and numbers: every repository is addressed by two parameters, owner (a user or organization name) and repo, the two parts of https://host/owner/repo. Issues and pull requests share one number sequence per repository (index, the 42 in #42). Gitea treats a pull request as an issue too: gitea_get_issue and gitea_list_issue_comments work with a pull request number for its title, labels and conversation, while gitea_get_pull_request, gitea_get_pull_request_files and gitea_get_pull_request_diff give the code side.

Finding things: gitea_search_repositories searches the whole instance, gitea_list_my_repositories, gitea_list_organization_repositories and gitea_list_user_repositories list by owner. gitea_search_issues searches issues and pull requests across all repositories and answers what is assigned to the token's user (assigned), created by them (created) or waits for their review (review_requested). Use gitea_get_repository first when you need the default branch.

Reviewing a pull request: gitea_get_pull_request (check mergeable and merged), then gitea_get_pull_request_files, gitea_get_pull_request_diff, gitea_list_pull_request_commits, gitea_list_pull_request_reviews and gitea_list_issue_comments. A diff over 200 KB is cut: open the pull request's html_url for the rest.

Reading code: gitea_get_tree lists files and folders at a branch, tag or commit (pass the branch name as sha), gitea_get_file_content returns a file as text (cut at 200 KB), gitea_list_branches, gitea_list_commits and gitea_get_commit show the history.

Releases: gitea_get_latest_release answers what the current version is, gitea_list_releases and gitea_get_release_by_tag show release notes and attached files.

Pagination: list tools take page (from 1) and limit. A server answers 30 items per page by default and at most 50 (its MAX_RESPONSE_ITEMS), so ask for the next page instead of a bigger limit. A list is returned under data (the repository search already does), together with _headers carrying x-total-count and link, and _pagination with nextCursor, the next page number. _pagination is missing on the last page. Comments and gitea_get_tree have their own paging, see their descriptions.

Errors: 401 means the token is wrong, expired or deleted, or GITEA_URL points at another server. 403 means the token lacks a scope this call needs (Gitea names it in the message), for example read:issue for issues or read:organization for organizations. 404 means the repository, issue or file does not exist or the user cannot see it: Gitea answers 404 for private resources it hides. 422 names a missing or invalid field.

Out of scope here: creating or editing issues, comments, pull requests, releases, branches and files, merging or approving, Actions runs and workflows, packages, wikis, notifications, webhooks, deploy keys and administration.