mcpField
G
Gitee MCP Server

Gitee MCP Server

Local
npmjs.comVersion Control7Updated 84w ago

About Gitee MCP Server

Gitee MCP Server exposes Gitee repository, issue, and pull request operations to AI clients. It also supports branch and file management, plus retrieval of user information.

Key features

  1. 01Create and fork repositories
  2. 02Create and inspect branches
  3. 03Read and update repository files
  4. 04Create and manage issues
  5. 05Create and manage pull requests
  6. 06Retrieve Gitee user details

Use cases

  1. 01Create or fork a Gitee repository
  2. 02Inspect branches and edit repository files
  3. 03Track issues and add comments
  4. 04Review or merge pull requests

MCP support

Provides MCP tools for operating on Gitee repositories, branches, files, issues, pull requests, and user information. It runs over stdio for use as a subprocess by MCP clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"gitee": {
"command": "npx",
"args": [
"-y",
"@smithery/cli"
]
}
}
}
Run commandnpx -y @smithery/cli

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@smithery/cli

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Gitee MCP Server

Let AI operate Gitee repositories/Issues/Pull Requests for you through MCP

Node Version NPM Version Docker Pulls Docker Image Version LICENSE smithery badge

README image


Supported AI Operations

CategoryMCP ToolDescription
Repository Operationscreate_repositoryCreate a Gitee repository
fork_repositoryFork a Gitee repository
Branch Operationscreate_branchCreate a new branch in a Gitee repository
list_branchesList branches in a Gitee repository
get_branchGet details of a specific branch in a Gitee repository
File Operationsget_file_contentsGet contents of a file or directory in a Gitee repository
create_or_update_fileCreate or update a file in a Gitee repository
push_filesPush multiple files to a Gitee repository
Issue Operationscreate_issueCreate an Issue in a Gitee repository
list_issuesList Issues in a Gitee repository
get_issueGet details of a specific Issue in a Gitee repository
update_issueUpdate an Issue in a Gitee repository
add_issue_commentAdd a comment to an Issue in a Gitee repository
Pull Request Operationscreate_pull_requestCreate a Pull Request in a Gitee repository
list_pull_requestsList Pull Requests in a Gitee repository
get_pull_requestGet details of a specific Pull Request in a Gitee repository
update_pull_requestUpdate a Pull Request in a Gitee repository
merge_pull_requestMerge a Pull Request in a Gitee repository
User Operationsget_userGet Gitee user information
get_current_userGet authenticated Gitee user information

Usage

Installing via Smithery

To install Gitee MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @normal-coder/gitee-mcp-server --client claude
Configuration
  • GITEE_API_BASE_URL: Optional, Gitee OpenAPI Endpoint, default is https://gitee.com/api/v5
  • GITEE_PERSONAL_ACCESS_TOKEN: Required, Gitee account personal access token (PAT), can be obtained from Gitee account settings Personal Access Tokens
  • DEBUG: Optional, set to true to enable debug logging, default is disabled
Run MCP Server via NPX
{
  "mcpServers": {
    "Gitee": {
      "command": "npx",
      "args": [
        "-y",
        "gitee-mcp-server"
      ],
      "env": {
        "GITEE_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}
Run MCP Server via Docker Container
  1. Get Docker Image
# Get from DockerHub
docker pull normalcoder/gitee-mcp-server

# Build locally
docker build -t normalcoder/gitee-mcp-server .
  1. Configure MCP Server
{
  "mcpServers": {
    "Gitee": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "GITEE_PERSONAL_ACCESS_TOKEN",
        "normalcoder/gitee-mcp-server"
      ],
      "env": {
        "GITEE_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

Development Guide

Install Dependencies
npm install
Build
npm run build

After successful build, /dist will contain the runnable MCP server.

Run Server
npm start

The MCP server will run on stdio, allowing it to be used as a subprocess by MCP clients.

Build Docker Image

You can also run the server using Docker:

docker build -t normalcoder/gitee-mcp-server .

Run MCP Server with Docker:

docker run -e GITEE_PERSONAL_ACCESS_TOKEN=<YOUR_TOKEN> normalcoder/gitee-mcp-server
Debug MCP Server

You can use @modelcontextprotocol/inspector for debugging:

Create a .env file in the root directory for environment variables:

GITEE_API_BASE_URL=https://gitee.com/api/v5
GITEE_PERSONAL_ACCESS_TOKEN=<YOUR_TOKEN>

Run the debug tool to start the service and web debug interface:

npx @modelcontextprotocol/inspector npm run start --env-file=.env

The project includes a debug() function for printing debug information, usage:

import { debug } from './common/utils.js';

debug('Message to log');
debug('Message with data:', { key: 'value' });

Debug logs are only printed when the DEBUG environment variable is set to true.

Dependencies

  • @modelcontextprotocol/sdk: MCP SDK for server implementation
  • universal-user-agent: For generating user agent strings
  • zod: For schema validation
  • zod-to-json-schema: For converting Zod schemas to JSON schemas

License

Licensed under MIT License. You are free to use, modify and distribute the software, subject to the terms and conditions of the MIT License. For more details, see the LICENSE file in the project repository.

Related Links

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.