oschina/mcp-gitee

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.
Features
- 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
Practical scenario: Obtain Issue from the repository, implement and create a Pull Request
1. Get repository Issues
2. Implement coding & create Pull Request based on Issue details
3. Comment & Close Issue
Installation
The Remote MCP Server requires no installation and works out of the box. To run mcp-gitee locally (stdio), pick one of the options below.
Remote MCP Server (Recommended)
Add the following to the mcpServers section of your host config, replacing with a token from here:
For per-client config file paths and formats (Claude Code, Codex, Cursor, Trae, Cline, Continue, opencode), follow the guides linked in the MCP Hosts Configuration section below.
Local (stdio)
Download Pre-built Binaries
Grab the archive for your platform (linux-amd64 / linux-arm / darwin-amd64 / darwin-arm64 / windows-amd64) from Releases, extract it, and put mcp-gitee on your PATH (on Windows the executable is mcp-gitee.exe).
Use npx
No installation needed; the pre-built binary for your platform is downloaded automatically at startup:
Building from Source
Requires Go 1.23.0 or higher.
1. Clone the repository:
2. Build the project:
Move ./bin/mcp-gitee PATH env
Use go install
Use the Installed Executable
Once mcp-gitee is available on your PATH (via Releases, source build, or go install):
> **Windows**: the executable must include the .exe suffix, and the path in command should use forward slashes / (Windows accepts them, and it avoids JSON backslash-escaping mistakes):
>
>
MCP Hosts Configuration
Config examples: Click to view more application configuration
- Claude Code
- Codex
- Cursor
- Trae
- Cline
- Continue
- opencode
Command-line Options
- --token: Gitee access token
- --api-base: Gitee API base URL (default: https://gitee.com/api/v5)
- --version: Show version information
- --transport: Transport type (stdio、sse or http, default: stdio)
- --address: The host and port to start the server on (default: localhost:8000)
- --enabled-toolsets: Comma-separated list of tools to enable (if specified, only these tools will be enabled)
- --disabled-toolsets: Comma-separated list of tools to disable
Environment Variables
You can also configure the server using environment variables:
- GITEE_ACCESS_TOKEN: Gitee access token
- GITEE_API_BASE: Gitee API base URL
- ENABLED_TOOLSETS: Comma-separated list of tools to enable
- DISABLED_TOOLSETS: Comma-separated list of tools to disable
Toolset Management
Toolset management supports two modes:
1. Enable specified tools (whitelist mode):
- Use --enabled-toolsets parameter or ENABLED_TOOLSETS environment variable
- Specify after, only listed tools will be enabled, others will be disabled
- Example: --enabled-toolsets="list_user_repos,get_file_content"
2. Disable specified tools (blacklist mode):
- Use --disabled-toolsets parameter or DISABLED_TOOLSETS environment variable
- Specify after, listed tools will be disabled, others will be enabled