Mcp Gitee

What is Mcp Gitee about?

Mcp Gitee offers a Model Context Protocol (MCP) server implementation that connects AI assistants with Gitee's REST API. It exposes a wide set of actions—such as repository listing, file retrieval, issue handling, and pull‑request management—through a standardized toolset.

How to use Mcp Gitee?

1. Installation – The server can be run directly via npx without a prior build:

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

   Or install globally with go install gitee.com/oschina/mcp-gitee@latest.
2. Configuration – Supply the Gitee access token and optional API base URL via environment variables or command‑line flags:
   • GITEE_ACCESS_TOKEN (or --token)
   • GITEE_API_BASE (default https://gitee.com/api/v5)
3. Running – Start the server (default localhost:8000) or let an AI host invoke it through the MCP endpoint.
4. Tool selection – Enable or disable specific tools with --enabled-toolsets / --disabled-toolsets or the corresponding environment variables.

Key Features

• Full coverage of Gitee repository, issue, pull‑request, and notification operations.
• Configurable API base URL for self‑hosted Gitee instances.
• Simple CLI flags and environment‑variable configuration.
• Dynamic toolset control (whitelist or blacklist mode).
• Supports personal, organization, and enterprise scopes.
• Multiple transport options: stdio, SSE, or HTTP.

Use Cases

• An AI coding assistant automatically creates a branch, implements a feature, opens a pull request, and closes the related issue.
• Continuous‑integration bots retrieve repository files, run tests, and publish releases.
• Notification aggregators fetch user notifications and summarize them for downstream services.
• Custom workflows that need to fork repositories, comment on pull requests, or manage releases across several Gitee projects.

FAQ

Q: Do I need to build the binary before using it? A: No. The npx command runs the latest package version directly. Building is optional for custom deployments.

Q: Which environment variables are required? A: GITEE_ACCESS_TOKEN is mandatory for authentication. GITEE_API_BASE is optional if you use the default Gitee API endpoint.

Q: How can I limit the exposed tools? A: Use --enabled-toolsets (whitelist) or --disabled-toolsets (blacklist). If both are provided, the whitelist takes precedence.

Q: Can I run the server on a custom host/port? A: Yes. Use the --address flag, e.g., --address 0.0.0.0:9000.

Q: What transport types are available? A: stdio (default), sse, and http.

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.