Gitee MCP Server

What is 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. It is intended for developers and teams using Gitee who want to automate workflows via MCP-compatible hosts like Claude, Cursor, or Codex.

How to use Gitee MCP Server?

You can use the server either as a remote MCP service (no installation required) or run it locally after building from source. For the remote server, configure your MCP host with the URL https://api.gitee.com/mcp and a Bearer token from your Gitee personal access tokens. For local use, clone the repository, build with make build, and run mcp-gitee with flags such as --token, --api-base, --transport, and --address. Tools can be enabled or disabled via command-line flags or per-request HTTP headers.

Use cases of Gitee MCP Server

• Automatically fetch repository issues, implement changes, create pull requests, and close issues.
• Search open source repositories or files by content on Gitee.
• Manage releases, compare branches, and merge pull requests without manual API calls.
• Filter available tools dynamically to restrict operations per request.

FAQ from Gitee MCP Server

What are the prerequisites for running the server locally?

Go 1.23.0 or higher and a Gitee account with a personal access token are required.

Can I use Gitee MCP Server without installing anything?

Yes, the official remote MCP server is available at https://api.gitee.com/mcp. No local installation is needed; just configure your MCP host with the correct URL and authorization header.

What transport types are supported?

The server supports stdio, sse, and http transports, configurable via the --transport flag.

How do I enable or disable specific tools?

You can use the --enabled-toolsets (whitelist) or --disabled-toolsets (blacklist) command-line flags, or the corresponding environment variables. When using the remote HTTP/SSE server, you can also pass X-MCP-Enabled-Tools or X-MCP-Disabled-Tools headers per request. Whitelist takes precedence over blacklist.

Is there a way to restrict operations on a per-request basis?

Yes, when using the remote MCP server (HTTP/SSE transport), you can dynamically filter tools by adding the X-MCP-Enabled-Tools or X-MCP-Disabled-Tools HTTP headers with a comma-separated list of tool names.