What is Gitee MCP Server

Gitee MCP Server is an implementation of the Model Context Protocol (MCP) tailored for Gitee. It facilitates interaction with Gitee’s API, enabling AI assistants to manage repositories, issues, pull requests, and notifications, enhancing developer productivity and collaboration.

Use cases

Gitee MCP Server can be utilized for various operations such as retrieving repository issues, coding implementations based on those issues, creating and managing pull requests, commenting on issues, and closing them. It caters to personal repositories, organizational projects, and enterprise operations.

How to use

To use Gitee MCP Server, you can install it via npx or build it from source using Go. After installation, configure it with your Gitee access token and API base URL. Command-line flags and environment variables allow for further customization of the server’s settings and toolsets.

Key features

Key features of Gitee MCP Server include dynamic interaction with Gitee repositories, support for configurable API base URLs, command-line configurations, and the ability to enable or disable specific toolsets for streamlined operations. It is designed to support personal, organizational, and enterprise-level tasks efficiently.

Where to use

Gitee MCP Server is particularly useful in software development environments where Gitee is used for source code management. It’s ideal for projects involving collaboration among team members, tracking issues, managing pull requests, and automating workflows within Gitee repositories.

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

Installation(This step can be skipped directly when starting npx)

Prerequisites

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

Building from Source

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

Usage

Check mcp-gitee version:

mcp-gitee --version

MCP Hosts Configuration

config example: Click to view more application configuration

• Connect to the official remote mcp-gitee server (no installation required)

{
  "mcpServers": {
    "gitee": {
      "url": "https://api.gitee.com/mcp",
      "headers": {
        "Authorization": "Bearer <your personal access token>"
      }
    }
  }
}

• npx

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

• executable

{
  "mcpServers": {
    "gitee": {
      "command": "mcp-gitee",
      "env": {
        "GITEE_API_BASE": "https://gitee.com/api/v5",
        "GITEE_ACCESS_TOKEN": "<your personal access token>"
      }
    }
  }
}

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
   • Example: --disabled-toolsets="list_user_repos,get_file_content"

Note:

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

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.