mcp-gitee

Gitee MCP Server

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:

{
  "mcpServers": {
    "gitee": {
      "url": "https://api.gitee.com/mcp",
      "headers": {
        "Authorization": "Bearer "
      }
    }
  }
}

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:

{
  "mcpServers": {
    "gitee": {
      "command": "npx",
      "args": [
        "-y",
        "@gitee/mcp-gitee@latest"
      ],
      "env": {
        "GITEE_API_BASE": "https://gitee.com/api/v5",
        "GITEE_ACCESS_TOKEN": ""
      }
    }
  }
}

Building from Source

Requires Go 1.23.0 or higher.

1. Clone the repository:

git clone https://gitee.com/oschina/mcp-gitee.git
   cd mcp-gitee

2. Build the project:

make build

Move ./bin/mcp-gitee PATH env

Use go install

go install gitee.com/oschina/mcp-gitee@latest

Use the Installed Executable

Once `mcp-gitee` is available on your PATH (via Releases, source build, or `go install`):

{
  "mcpServers": {
    "gitee": {
      "command": "mcp-gitee",
      "env": {
        "GITEE_API_BASE": "https://gitee.com/api/v5",
        "GITEE_ACCESS_TOKEN": ""
      }
    }
  }
}

> 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):

>

> ```json

> {

> "mcpServers": {

> "gitee": {

> "command": "C:/Users//bin/mcp-gitee.exe",

> "env": {

> "GITEE_ACCESS_TOKEN": ""

> }

> }

> }

> }

> ```

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):

2. Disable specified tools (blacklist mode):

Note:

• If both `enabled-toolsets` and `disabled-toolsets` are specified, `enabled-toolsets` takes precedence
• Tool names are case-sensitive

Per-Request Tool Filtering (HTTP Headers)

When using the remote MCP server (HTTP/SSE transport), you can dynamically filter available tools on a per-request basis via HTTP headers. This is useful for clients that need fine-grained control over tool exposure without restarting the server.

1. Enable specified tools via header (whitelist):

2. Disable specified tools via header (blacklist):

Priority rules:

• If both `X-MCP-Enabled-Tools` and `X-MCP-Disabled-Tools` are present in the same request, the whitelist (`X-MCP-Enabled-Tools`) takes precedence
• Tool names are case-sensitive

Example configuration for Cursor/Claude:

{
  "mcpServers": {
    "gitee": {
      "url": "https://api.gitee.com/mcp",
      "headers": {
        "Authorization": "Bearer ",
        "X-MCP-Enabled-Tools": "list_user_repos,get_file_content,list_repo_issues"
      }
    }
  }
}

License

This project is licensed under the MIT License. See the LICENSE file for more details.

Available Tools

The server provides various tools for interacting with Gitee:

Contribution

We welcome contributions from the open-source community! If you'd like to contribute to this project, please follow these guidelines:

1. Fork the repository.

2. Create a new branch for your feature or bug fix.

3. Make your changes and ensure the code is well-documented.

4. Submit a pull request with a clear description of your changes.

For more information, please refer to the CONTRIBUTING file.