Gitea MCP Server

Production-ready MCP server for Gitea integration. That is what the gitea mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

A production-ready Model Context Protocol (MCP) server for seamless integration with self-hosted Gitea platforms. This server provides tools for creating repositories and uploading files while preserving directory structure.

• Repository Creation — Create new repositories on any configured Gitea instance
• File Upload — Upload files and folders while preserving directory structure
• Project Sync — Automatically sync entire projects for initial commits (new files only)
• Advanced File Updates — Smart update tool with conflict resolution for modifying existing files
• Multi-Instance Support — Connect to multiple Gitea instances simultaneously
• Rate Limiting — Respect API rate limits per instance

The tools it exposes

The server publishes 6 tools. What each one is for:

• Prerequisites — The Prerequisites tool exposed by this server
• Installation — 1. Clone the repository: bash git clone cd gitea-mcp
• create_repository — The create_repository tool exposed by this server
• upload_files — Upload multiple files to a repository while preserving directory structure
• Scripts — The Scripts tool exposed by this server
• Logging — The Logging tool exposed by this server

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: LOG_LEVEL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js 18.0.0 or higher - Access to one or more Gitea instances - Personal access tokens for authentication

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Gitea MCP's toolset — Prerequisites, Installation, create_repository and 3 more — is a fair guide to whether it matches your workflow. It is maintained by MushroomFleet; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.