Production-ready MCP server for Gitea integration
Production-ready MCP server for Gitea integration
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.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| instanceId | string, required): Gitea instance identifier |
| owner | string, required): Repository owner username |
| repository | string, required): Repository name |
| files | array, required): Array of file operation objects |
| message | string, required): Commit message for all operations |
| branch | string, default: "main"): Target branch |
| projectPath | string, default: "."): Path to project directory to sync |
| dryRun | boolean, default: false): Preview operations without making changes |
| includeHidden | boolean, default: false): Include hidden files (starting with .) |
| maxFileSize | number, default: 1048576): Maximum file size in bytes (1MB) |
| textOnly | boolean, default: true): Only upload text files (skip binary files) |
| strategy | string, default: "auto"): Update strategy: 'auto', 'batch', or 'individual' |
| conflictResolution | string, default: "fail"): Conflict handling: 'fail', 'overwrite', or 'skip' |
| detectChanges | boolean, default: true): Compare with remote files to avoid unnecessary updates |
| add | Create new files (equivalent to POST API) |
| modify | Update existing files (uses PUT API with SHA for conflict resolution) |
| delete | Remove existing files (uses DELETE API with SHA) |
| auto | Intelligently chooses the best approach based on file count and operation types |
| batch | Performs all operations in a single commit using Gitea's batch API |
| individual | Performs each operation as a separate commit |
| create_repository | |
| upload_files |
{
"mcpServers": {
"gitea-mcp": {
"command": "node",
"args": [
"./build/index.js"
],
"cwd": "/path/to/gitea-mcp",
"env": {
"NODE_ENV": "production",
"LOG_LEVEL": "info"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| NODE_ENV | Declared in the maintainer’s client configuration. | Check documentation |
| LOG_LEVEL | Declared in the maintainer’s client configuration. | Check documentation |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
Connect GitHub MCP to repositories, issues and pull requests with GitHub’s hosted service or a locally run server.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.