MCP.Market

Forgejo / Codeberg / Gitea MCP server

by brechanbech·io.github.brechanbech/forgejo-mcp-rs·v0.27.0

Model Context Protocol server for Forgejo, Codeberg and Gitea, in Rust

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

not scanned yet

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Forgejo / Codeberg / Gitea yet.

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

Forgejo / Codeberg / Gitea tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Forgejo / Codeberg / Gitea compares

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

Safety score
88/100
higher than 80% of 4,460 AI and agents servers

Release history: 5 versions in the registry since 2026-09-27, latest 2026-10-29, typically one every 3 days.

Install Forgejo / Codeberg / Gitea in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Forgejo / Codeberg / Gitea repository's README, as published. We do not edit it. Read it on GitHub

forgejo-mcp-rs

A Model Context Protocol server for Forgejo, Codeberg and Gitea. It lets an MCP client (Claude Code, Claude Desktop, …) read your forge — the authenticated user, repositories, issues, and pull requests — over the Forgejo/Gitea REST API.

Status: read-only by default, with opt-in guarded writes (since v0.2). Read tools across

the forge — user, repos, issues, pull requests, search, orgs, notifications, comments,

reviews, and Actions (CI) runs — plus guarded writes (createrepo, editrepo,

createbranch, createissue, createpullrequest, commentonissue, delete_repo,

migrate_repo, push-mirror

management, and dispatch_workflow) gated behind a separate write token and a deliberate,

time-boxed write mode. See SPECIFICATION.md for the full design.

It speaks the Forgejo REST API directly through a small, in-house client (src/forgejo/client.rs, over the src/mcpcore/ transport) — an independent implementation over the documented API**, not a port of any other server. There is no third-party forge SDK in the trust path, so the tool surface holding your token is code you can read and audit end to end.

The server speaks MCP protocol version 2026-07-28 (since v0.16) and negotiates down to 2024-11-05, so older clients keep working unchanged. It runs over stdio and exposes tools only — no resources, prompts, sampling, or roots.

Build

cargo build --release   # target/release/forgejo-mcp-rs
cargo install --path .  # install to ~/.cargo/bin

Woodpecker CI

A companion server for Woodpecker CI shipped in this crate as a second woodpecker-mcp binary from v0.13.0 through v0.17.0. It now lives in its own repository and crate: woodpecker-mcp.

Woodpecker is its own system — it drives Gitea, GitHub, GitLab, and Bitbucket as readily as Forgejo, and that server never called the Forgejo API at all — so bundling it here made it invisible to everyone not running Forgejo. Nothing about it changed in the move; if you were using the woodpecker-mcp binary from this crate, install it from the new crate instead and point your MCP client at the new path.

Configure

The server is configured by environment variables:

Shortened. The full README is on GitHub.

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

Forgejo / Codeberg / Gitea: common questions

Is Forgejo / Codeberg / Gitea MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Forgejo / Codeberg / Gitea safety report
Does Forgejo / Codeberg / Gitea need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Forgejo / Codeberg / Gitea maintained?
The last commit was 38 days ago (2026-09-27). The latest release is v0.27.0.

More from brechanbech →