Gitee Enterprise MCP Server

Gitee Enterprise MCP Server is a Model Context Protocol (MCP) server implementation for Gitee Enterprise. It provides a set of tools for interacting with Gitee Enterprise API, allowing AI assistants to manage enterprise repositories, issues, pull requests, and more.

Features

• Interact with Gitee Enterprise repositories, issues, pull requests
• Support for enterprise-level operations and management
• Configurable API base URL to support different Gitee Enterprise instances
• Support for SSE and Stdio transport
• Dynamic toolset enable/disable

Scenario Example

1. Get specific enterprise issues

2. Improve the issue content

3. Divide subtasks

4. Create PR/Review PR

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

Prerequisites

• Go 1.23.0 or higher
• MCP token, Go to get

Building from Source

1. Clone the repository:

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

2. Build the project:

make build

Move ./bin/mcp-gitee-ent PATH env

Use go install

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

Usage

Check mcp-gitee-ent version:

mcp-gitee-ent --version

MCP Hosts Configuration

Config example:

• npx

{
  "mcpServers": {
    "gitee-ent": {
      "command": "npx",
      "args": [
        "-y",
        "@gitee/mcp-gitee-ent@latest"
      ],
      "env": {
         "GITEE_ENT_API_BASE": "https://api.gitee.com/enterprises",
         "GITEE_ENT_MCP_ACCESS_TOKEN": ""
      }
    }
  }
}

• executable

{
  "mcpServers": {
    "gitee-ent": {
      "command": "mcp-gitee-ent",
      "env": {
        "GITEE_ENT_API_BASE": "https://api.gitee.com/enterprises",
        "GITEE_ENT_MCP_ACCESS_TOKEN": "",
      }
    }
  }
}

Command-line Options

• --token: access token
• --api-base: Gitee Ent API base URL (default: https://api.gitee.com/enterprises)
• --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)
• --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_ENT_MCP_ACCESS_TOKEN: Gitee MCP ent access token
• GITEE_ENT_API_BASE: Gitee ENT 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="update_enterprise_issue,list_enterprise_repositories"

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="update_enterprise_issue,list_enterprise_repositories"

Note:

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

Available Tools

The server provides various tools for interacting with Gitee Enterprise:

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.