Navigation
Gitee MCP Server: MCP-Powered Repo & PR Automation - MCP Implementation

Gitee MCP Server: MCP-Powered Repo & PR Automation

Gitee MCP Server empowers AI assistants to manage repositories, issues, and PRs via Gitee's API, streamlining workflows with MCP integration.

Developer Tools
4.2(103 reviews)
154 saves
72 comments

34% of users reported increased productivity after just one week

About Gitee MCP Server

What is Gitee MCP Server: MCP-Powered Repo & PR Automation?

This tool bridges AI assistants with Gitee's ecosystem by implementing the Model Context Protocol (MCP). Think of it as a middleman that lets your AI automate tasks like managing repositories, handling pull requests, and even commenting on issues—all without leaving your workflow. Instead of manually clicking through Gitee’s UI, the server talks directly to Gitee’s API, saving you time for actual coding.

How to use Gitee MCP Server: Step-by-Step Playbook

First, grab the server via go install (my go-to method—it’s faster than building from source). Then configure it with your access token. For example, setting up Cursor or Windsurf involves pasting a JSON snippet that points to your Gitee API endpoint. Once running, you can trigger actions like create_pull or merge_pull directly from your AI interface. Pro tip: Use the --sse-address flag if you’re debugging locally—it makes logs way easier to track.

Gitee MCP Server Features

Key Features of Gitee MCP Server: What Makes It Shine?

Flexibility is its superpower. Not only does it handle personal repos, but it also plays nice with orgs and enterprises. My favorite? The configurable API base URL—perfect if your company runs a private Gitee instance. Oh, and the CLI flags? They’re a lifesaver for quick setups. No more digging through YAML files every time you test a new token.

Use Cases: Real-World Magic Moments

Imagine this: Your AI spots an open issue, grabs the details, codes a fix, and auto-creates a PR—all in one workflow. The server even closes the original issue once the PR is merged. Another win? Automating release management—list, create, or update releases without leaving your terminal. I’ve used it to bulk-comment on outdated PRs, which saved me hours during a team cleanup.

Gitee MCP Server FAQ

FAQ from Gitee MCP Server: Answers to Your Questions

Does it support multiple Gitee accounts? Yep! Just spin up separate instances with different tokens.
Can I debug API calls? Absolutely. The --transport flag switches between stdio and SSE modes for better visibility.
Why use this over Gitee’s native API? It’s MCP-integrated, so it’s AI-ready out of the box. Plus, the pre-built tools (like list_user_repos) save you from writing boilerplate code.

Content

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
Practical scenario: Obtain Issue from the repository, implement and create a Pull Request
  1. Get repository Issues get_repo_issues
  2. Implement coding & create Pull Request based on Issue details implement_issue
  3. Comment & Close Issue comment_and_close_issue

Installation

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
  1. 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

CursorWindsurf config example:

{
  "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 or sse, default: stdio)
  • -sse-address: The host and port to start the SSE server on (default: localhost:8000)

Environment Variables

You can also configure the server using environment variables:

  • GITEE_ACCESS_TOKEN: Gitee access token
  • GITEE_API_BASE: Gitee API base URL

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
create_release Repository Create a release for a repository
list_releases Repository List repository releases
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
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
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.

Related MCP Servers & Clients