Gitee MCP Server

What is Gitee MCP Server about?

Gitee MCP Server implements the Model Context Protocol for Gitee, exposing a programmable interface that AI assistants can call to perform common repository actions such as listing repos, creating issues, handling pull requests, and more.

How to use Gitee MCP Server?

1. Installation – either run the binary directly, install via go install, or use the recommended npx command:

   {
     "command": "npx",
     "args": ["-y", "@gitee/mcp-gitee@latest"]
   }
   

2. Configuration – set the Gitee API base URL and a personal access token via environment variables or command‑line flags (--token, --api-base). Example using environment variables:

   export GITEE_API_BASE="https://gitee.com/api/v5"
   export GITEE_ACCESS_TOKEN="<your token>"
   mcp-gitee --address localhost:8000
   

3. Running – start the server (mcp-gitee) or let a client invoke it through the MCP host configuration defined in a JSON file.

Key Features of Gitee MCP Server

• Full coverage of Gitee repository management: list repos, get file contents, create/fork repos, releases.
• Comprehensive issue and pull‑request tooling: create, update, comment, merge, list, retrieve diffs.
• User and notification utilities.
• Configurable toolset enable/disable via --enabled-toolsets / --disabled-toolsets or corresponding environment variables.
• Supports personal, organization, and enterprise scopes.
• Multiple transport modes (stdio, SSE, HTTP).

Use Cases of Gitee MCP Server

• AI‑driven coding assistants that automatically generate code, open issues, and submit pull requests on Gitee.
• CI/CD bots that publish releases or tag commits after successful builds.
• Project automation such as nightly repository scans, stale‑issue closing, or bulk repo creation for new teams.
• Notification aggregators that collect and present user notifications in a unified dashboard.

FAQ from the Gitee MCP Server

Q: Which Go version is required? A: Go 1.23.0 or newer.

Q: Can I run the server without installing anything locally? A: Yes, use the npx method which fetches the latest package and runs it directly.

Q: How do I limit the tools exposed to an AI assistant? A: Use --enabled-toolsets to whitelist or --disabled-toolsets to blacklist specific tool names; the whitelist takes precedence if both are set.

Q: Where do I find the list of available tool names? A: The README includes a table of all tools with their categories and descriptions.

Q: Is the server open‑source? A: Yes, it is licensed under the MIT License and hosted at https://github.com/oschina/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

1. Get repository Issues
2. Implement coding & create Pull Request based on Issue details
3. Comment & Close Issue

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:

Tool	Category	Description
list_user_repos	Repository	List user authorized repositories
get_file_content	Repository	Get the content of a file in a repository
create_user_repo	Repository	Create a user repository
create_org_repo	Repository	Create an organization repository
create_enter_repo	Repository	Create an enterprise repository
fork_repository	Repository	Fork a repository
create_release	Repository	Create a release for a repository
list_releases	Repository	List repository releases
search_open_source_repositories	Repository	Search open source repositories on Gitee
list_repo_pulls	Pull Request	List pull requests in a repository
merge_pull	Pull Request	Merge a pull request
create_pull	Pull Request	Create a pull request
update_pull	Pull Request	Update a pull request
get_pull_detail	Pull Request	Get details of a pull request
comment_pull	Pull Request	Comment on a pull request
list_pull_comments	Pull Request	List all comments for a pull request
get_diff_files	Pull Request	Get a pull request diff files
create_issue	Issue	Create an issue
update_issue	Issue	Update an issue
get_repo_issue_detail	Issue	Get details of a repository issue
list_repo_issues	Issue	List repository issues
comment_issue	Issue	Comment on an issue
list_issue_comments	Issue	List comments on an issue
get_user_info	User	Get current authenticated user information
search_users	User	Search for users
list_user_notifications	Notification	List user notifications

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.