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.

[](https://cursor.com/en/install-mcp?name=gitee&config=eyJ1cmwiOiJodHRwczovL2FwaS5naXRlZS5jb20vbWNwIiwiaGVhZGVycyI6eyJBdXRob3JpemF0aW9uIjoiQmVhcmVyIDx5b3VyIHBlcnNvbmFsIGFjY2VzcyB0b2tlbj4ifX0%3D)

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

Practical scenario: Obtain Issue from the repository, implement and create a Pull Request

1. Get repository Issues

1. Implement coding & create Pull Request based on Issue details

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

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

1. Build the project:

``bash make build `` Move ./bin/mcp-gitee PATH env

Use go install

``bash go install gitee.com/oschina/mcp-gitee@latest ``

Usage

Check mcp-gitee version:

mcp-gitee --version

MCP Hosts Configuration

Config examples: [Click to view more application configuration](./docs/install/)

• [Claude Code](./docs/install/claude.md)
• [Codex](./docs/install/codex.md)
• [Cursor](./docs/install/cursor.md)
• [Trae](./docs/install/trae.md)
• [Cline](./docs/install/cline.md)
• [Continue](./docs/install/continue.md)
• [opencode](./docs/install/opencode.md)

Remote MCP Server

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

{
  "mcpServers": {
    "gitee": {
      "url": "https://api.gitee.com/mcp",
      "headers": {
        "Authorization": "Bearer "
      }
    }
  }
}

Codex uses ~/.codex/config.toml:

[mcp_servers.gitee]
url = "https://api.gitee.com/mcp"
bearer_token_env_var = "GITEE_ACCESS_TOKEN"

opencode uses ~/.config/opencode/opencode.json:

{
  "mcp": {
    "gitee": {
      "type": "remote",
      "url": "https://api.gitee.com/mcp",
      "headers": {
        "Authorization": "Bearer "
      },
      "enabled": true
    }
  }
}

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"

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

Per-Request Tool Filtering (HTTP Headers)

When using the remote MCP server (HTTP/SSE transport), you can dynamically filter available tools on a per-request basis via HTTP headers. This is useful for clients that need fine-grained control over tool exposure without restarting the server.

1. Enable specified tools via header (whitelist):

• Use the X-MCP-Enabled-Tools header
• Only the listed tools will be enabled for that request
• Example: X-MCP-Enabled-Tools: list_user_repos,get_file_content

1. Disable specified tools via header (blacklist):

• Use the X-MCP-Disabled-Tools header
• The listed tools will be disabled for that request
• Example: X-MCP-Disabled-Tools: create_repo,delete_repo

Priority rules:

• If both X-MCP-Enabled-Tools and X-MCP-Disabled-Tools are present in the same request, the whitelist (X-MCP-Enabled-Tools) takes precedence
• Tool names are case-sensitive

Example configuration for Cursor/Claude:

{
  "mcpServers": {
    "gitee": {
      "url": "https://api.gitee.com/mcp",
      "headers": {
        "Authorization": "Bearer ",
        "X-MCP-Enabled-Tools": "list_user_repos,get_file_content,list_repo_issues"
      }
    }
  }
}

License

This project is licensed under the MIT License. See the [LICENSE](LICENSE) file for more details.

Available Tools

The server provides various tools for interacting with Gitee:

| Tool | Category | Description | |-------------------------------------|----------|-------------| | listuserrepos | Repository | List user authorized repositories | | getfilecontent | Repository | Get the content of a file in a repository | | createrepo | Repository | Create a repository (user, org, or enterprise) | | forkrepository | Repository | Fork a repository | | createrelease | Repository | Create a release for a repository | | listreleases | Repository | List repository releases | | searchopensourcerepositories | Repository | Search open source repositories on Gitee | | searchfilesbycontent | Repository | Search files by content in a repository | | comparebranchestags | Repository | Compare two branches, tags, or commits in a repository | | listrepopulls | Pull Request | List pull requests in a repository | | mergepull | Pull Request | Merge a pull request | | createpull | Pull Request | Create a pull request | | updatepull | Pull Request | Update a pull request | | getpulldetail | Pull Request | Get details of a pull request | | getdifffiles | Pull Request | Get a pull request diff files | | managepullreview | Pull Request | Manage a pull request review (approve or cancel) | | createcomment | Comment | Create a comment on an issue or pull request | | listcomments | Comment | List all comments for an issue or pull request | | createissue | Issue | Create an issue | | updateissue | Issue | Update an issue | | getrepoissuedetail | Issue | Get details of a repository issue | | listrepoissues | Issue | List repository issues | | getuserinfo | User | Get current authenticated user information | | searchusers | User | Search for users | | listuser_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](CONTRIBUTING.md) file.

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: oschina
• Source: oschina/mcp-gitee
• License: MIT

Install and usage instructions live in the source repository linked above.