gitee

This Gitee MCP Server enables an AI to operate Gitee repositories, issues, pull requests, branches, files, and user information through the Model Context Protocol (MCP). It exposes a variety of tools such as create_repository, fork_repository, create_branch, list_branches, get_branch, file operations (get_file_contents, create_or_update_file, push_files), issue operations (create_issue, list_issues, get_issue, update_issue, add_issue_comment), pull request operations (create_pull_request, list_pull_requests, get_pull_request, update_pull_request, merge_pull_request), and user operations (get_user, get_current_user). You can run the server via NPX or Docker, supply your Gitee personal access token, and then call these tools through MCP clients. The server authenticates requests using your PAT and interacts with the Gitee API to perform the requested actions on your behalf. When using NPX, set GITEE_PERSONAL_ACCESS_TOKEN in the environment; when using Docker, pass it as an environment variable or via the container's env block so the server can authenticate to Gitee.

Prerequisites:

• Node.js v22.12.0 or newer (for development or NPX usage via Smithery integration)
• npm (comes with Node.js)
• Docker (optional, for containerized usage)

Install and run via NPX (recommended for quick start):

npx -y @normal-coder/gitee-mcp-server

Configure environment variable for authentication (example for NPX run):

GITEE_PERSONAL_ACCESS_TOKEN=<YOUR_TOKEN> npx -y gitee-mcp-server

Run via Docker (official image):

# Pull the image
docker pull normalcoder/gitee-mcp-server

# Run with token (example)
docker run -e GITEE_PERSONAL_ACCESS_TOKEN=<YOUR_TOKEN> normalcoder/gitee-mcp-server

Development build from source (optional):

npm install
npm run build

After building, the runnable MCP server will be in the dist directory and can be started as described in the project’s docs.

Environment variables and config tips:

• GITEE_API_BASE_URL: Optional. Default is https://gitee.com/api/v5
• GITEE_PERSONAL_ACCESS_TOKEN: Required for most operations. Keep this token secure.
• DEBUG: Optional. Set to true to enable debug logging.
• When using Docker, you can pass the token through the container environment or mount a .env file for convenience. Common issues:
• Invalid token or insufficient permissions: Ensure the PAT has appropriate scopes for repositories, issues, PRs, and user data.
• Network access to Gitee API: Ensure outbound network access from your runtime environment.
• On long-running actions, verify rate limits of the Gitee API and implement retry logic if needed.