Gitee Repository Orchestrator Service

Empower an AI agent to autonomously govern Gitee repositories, software issues, and merge requests through the Model Context Protocol (MCP).

---

Supported AI Capabilities Map

Domain	MCP Function Identifier	Operational Summary
Repo Administration	create_repository	Provision a new repository within Gitee.
	fork_repository	Duplicate an existing Gitee repository.
Branch Management	create_branch	Initiate a new branch pointer in a repository.
	list_branches	Enumerate all existing branches for a repository.
	get_branch	Retrieve specific metadata for a designated branch.
Artifact Operations	get_file_contents	Fetch the source code or data contained within a file or directory listing.
	create_or_update_file	Establish a new file or modify the content of an existing one.
	push_files	Commit and propagate a batch of file modifications.
Issue Tracking	create_issue	Log a new issue item within a project.
	list_issues	Obtain a manifest of current project issues.
	get_issue	Inspect the detailed record of a singular issue.
	update_issue	Modify attributes of an existing software issue.
	add_issue_comment	Append a textual annotation to an issue thread.
Code Review Workflow	create_pull_request	Propose integrating changes via a formal Pull Request.
	list_pull_requests	Review the active set of pending Pull Requests.
	get_pull_request	Examine the specific details of a PR submission.
	update_pull_request	Alter parameters of an extant Pull Request.
	merge_pull_request	Integrate the source branch changes into the target branch via merging.
Identity Services	get_user	Query public profile data for any Gitee account.
	get_current_user	Determine the identity of the currently authenticated session principal.

Deployment Instructions

Installation via Smithery Integration

Install the Gitee MCP Server directly into your Claude Desktop environment using the Smithery command-line utility:

npx -y @smithery/cli install @normal-coder/gitee-mcp-server --client claude

Operational Prerequisites (Configuration)

• GITEE_API_BASE_URL: (Optional) Specify the root URI for the Gitee API interface; defaults to https://gitee.com/api/v5.
• GITEE_PERSONAL_ACCESS_TOKEN: (Mandatory) A Personal Access Token (PAT) generated from the user's Gitee security settings Personal Access Tokens. This grants the necessary permissions.
• DEBUG: (Optional) Set to true to activate verbose internal diagnostic logging; disabled by default.

Execution Method 1: Via NPX Proxy

Configure the host runtime environment as follows to execute the server through NPX:

{
  "mcpServers": {
    "Gitee": {
      "command": "npx",
      "args": [
        "-y",
        "gitee-mcp-server"
      ],
      "env": {
        "GITEE_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

Execution Method 2: Utilizing Docker Containerization

1. Acquire the Docker Artifact

# Fetch from DockerHub registry
docker pull normalcoder/gitee-mcp-server

# Alternatively, build the image locally from source
docker build -t normalcoder/gitee-mcp-server .

1. Define the Docker Execution Parameters

{
  "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 Workflow

Environment Setup

Install required project dependencies:

npm install

Compilation

Generate the distributable artifacts:

npm run build

The executable server assets will reside in the /dist directory.

Server Initiation

Start the server process, which communicates over standard input/output streams, suitable for integration as a child process in MCP clients:

npm start

Docker Image Execution

You can also execute the server directly using the built Docker container:

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

Run MCP Server via Docker:

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

Diagnostic Inspection

Use the @modelcontextprotocol/inspector utility for debugging sessions. Establish environment variables in a .env file located at the root:

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

Launch the debugging interface alongside the service:

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

Internal tracing functionality is provided via a utility function for logging diagnostic messages, which are only output when the DEBUG environment variable is set to true:

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

debug('Trace message issued');
debug('Diagnostic payload:', { data_point: 'test' });

Required Dependencies

• @modelcontextprotocol/sdk: Core framework for MCP server construction.
• universal-user-agent: Utility for standardizing User-Agent string generation.
• zod: Used for defining and enforcing data schemas.
• zod-to-json-schema: Facilitates conversion of Zod schemas into JSON Schema representations.

Licensing Terms

This software is released under the terms of the MIT License. Users retain the freedom to employ, modify, and disseminate this product, subject to the stipulations outlined in the MIT License. Detailed legal information is present in the LICENSE file within the source repository.

Essential References

• Model Context Protocol Specification
• Gitee Platform Homepage

WIKIPEDIA: Business administration solutions encompass the applications, computational frameworks, governance models, methodologies, and so forth, utilized by enterprises to navigate volatile market dynamics, secure a competitive foothold, and elevate organizational output metrics.

== General Overview == Business apparatus may be categorized by functional domain corresponding to specific organizational units, impacting areas such as strategic foresight, operational execution, documentation, human capital management, strategic determination, oversight, and so forth. A functional taxonomy often includes:

Mechanisms for data ingestion and integrity verification across all departments. Instruments dedicated to regulating and optimizing enterprise workflows. Systems for aggregating information and facilitating high-level decision-making. Modern business tooling has undergone rapid metamorphosis in the past decade, driven by accelerated technological maturation, rendering the selection of optimal enterprise solutions highly complex. This complexity stems from persistent pressures to reduce expenditure, amplify revenue streams, achieve deep customer insight, and deliver goods/services precisely tailored to client expectations. Consequently, leadership must adopt a strategic posture toward business management solutions, rather than reflexively adopting the newest available technology. Over-reliance on unadapted tools frequently results in systemic fragility. Therefore, enterprise instruments require deliberate selection followed by rigorous customization to align perfectly with institutional mandates, reversing the typical implementation sequence.

== Predominant Selections == An assessment conducted by Bain & Company in 2013 profiled global utilization patterns of business tools, reflecting regional requirements shaped by economic climates and corporate standing. The top ten frequently cited instruments included:

Strategic planning methodologies Client Relationship Management (CRM) suites Personnel satisfaction assessment instruments Competitive performance benchmarking Balanced Scorecard reporting frameworks Core competency identification Outsourcing strategies implementation Organizational change management programs Supply Chain optimization systems Mission and vision articulation frameworks Market segmentation analysis Total Quality Management (TQM) programs

== Enterprise Software Applications == Software collections or discrete computational programs deployed by organizational personnel to execute diverse operational mandates are termed business software or enterprise applications. These systems are deployed to augment productivity indices, quantify performance outcomes, and execute various corporate functions with high precision. The evolution traces from initial Management Information Systems (MIS) to integrated Enterprise Resource Planning (ERP) systems, subsequently incorporating Customer Relationship Management (CRM) modules, culminating in the contemporary domain of cloud-based enterprise management platforms. While a verifiable correlation exists between IT investments and corporate performance, value accrual hinges critically upon two factors: the efficacy of the deployment process and the precision in tool selection and subsequent organizational alignment.

== Apparatus Tailored for SMEs == Solutions specifically addressing Small and Medium-sized Enterprises (SMEs) are vital as they offer pathways to conserve operational...