Gitee MCP Server

If you want an AI assistant working directly with Gitee, the gitee mcp server is the bridge. Gitee API integration, repository, issue, and pull request management, and more.

What Gitee does

Gitee MCP Server is a Model Context Protocol (MCP) server implementation for Gitee. It provides a set of tools for interacting with Gitee's API, allowing AI assistants to manage repositories, issues, pull requests, and more.

Key capabilities

• Interact with Gitee repositories, issues, pull requests, and notifications
• Configurable API base URL to support different Gitee instances
• Command-line flags for easy configuration
• Supports both personal, organization, and enterprise operations
• Dynamic toolset enable/disable

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• Example — --enabled-toolsets="list_user_repos,get_file_content"
• list_user_repos — Repository
• get_file_content — Repository
• create_repo — Repository
• fork_repository — Repository
• create_release — Repository
• list_releases — Repository
• search_open_source_repositories — Repository
• search_files_by_content — Repository
• compare_branches_tags — Repository
• list_repo_pulls — Pull Request
• merge_pull — Pull Request
• create_pull — Pull Request
• update_pull — Pull Request

Installing the gitee mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply one environment variable: GITEE_ACCESS_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Go 1.23.0 or higher - Gitee account with an access token, Go to get

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Gitee sits in that group, and the shape of its toolset — Example, list_user_repos, get_file_content among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Gitee.
• Written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the gitee mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.