Name: Gitee
Author: oschina

LABSCO SUMMARY

The issue-to-merge loop, closed inside the editor.

Reading an issue, opening the pull request against it, pulling the changed files, approving and merging with the related issue closed are all here, which is what makes this more than a read-only Gitee viewer. Two practical notes: the hosted endpoint means no install and no Go toolchain, and the allowlist and blocklist settings are worth using — a session that should only read repositories can be limited to exactly the tools that do so.

What it is

A Gitee server for repositories, issues, pull requests and notifications, available as a hosted endpoint or as a local binary. Which tools are exposed is configurable, by allowlist or blocklist.

What you get

Issues listed with filters on state, labels, assignee, deadline and schedule, read individually, created and updated — including issue type, milestone, program and collaborators
Pull requests listed by base, head, author, assignee, tester and state, created with reviewers, testers, labels and draft status, and updated afterwards
get_diff_files returns a pull request's changed files, and compare_branches_tags diffs two branches, tags or commits
manage_pull_review approves or cancels a review, and merge_pull merges with a merge method, optional source-branch pruning and closing the related issue
Comments listed and created on either an issue or a pull request, chosen by resource_type
search_files_by_content greps a repository at a given ref, with path filters and before and after context lines
get_file_content reads a file at a ref; create_repo makes a repository for a user, organization or enterprise; fork_repository forks one
Releases listed and created with tag, target commit and prerelease flag
list_user_notifications covers the authorized user's notifications, filtered to unread or participating; list_user_repos, search_open_source_repositories and search_users cover discovery
Toolsets narrowed with --enabled-toolsets as an allowlist or --disabled-toolsets as a blocklist, with the allowlist winning if both are given

Requirements

A Gitee account and a personal access token. The quickest route needs no install at all: point the client at the official remote server at https://api.gitee.com/mcp with the token as an Authorization: Bearer header. Running it yourself means Go 1.23.0 or higher — go install gitee.com/oschina/mcp-gitee@latest, or make build from a clone — with the token in --token or GITEE_ACCESS_TOKEN. --api-base (or GITEE_API_BASE) points at a different Gitee instance, defaulting to https://gitee.com/api/v5, and --transport selects stdio, sse or http with --address setting the bind, default localhost:8000.

Setup effort

One command plus a key — go install gitee.com/oschina/mcp-gitee@latest, then supply credentials

See installation options

USE CASES

01

Turning an issue into a merged change

Read the issue, open the pull request that implements it, and merge with the related issue closed and the source branch pruned.

get_repo_issue_detailcreate_pullmerge_pull

02

Reviewing a pull request you did not write

Read the detail and the changed files, leave a comment on it, then approve it.

get_pull_detailget_diff_filescreate_commentmanage_pull_review

03

Finding where something is implemented in an unfamiliar repository

Search file contents at a specific ref with context lines around each hit, then read the file that turns out to matter.

search_files_by_contentget_file_content

04

Catching up on what needs your attention

Read the unread notifications, then open the issues and pull requests behind them.

list_user_notificationslist_repo_issueslist_repo_pulls

05

Cutting a release

Compare the branch against the last tag to see what is going out, then create the release against that commit.

compare_branches_tagslist_releasescreate_release

06

Starting a new project on Gitee

Create the repository under a user, organization or enterprise, or fork an existing one to work from.

create_repofork_repositorylist_user_repos

25 tools

Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.

`compare_branches_tags`

Compare two branches, tags, or commits in a repository

BEFORE YOU INSTALL

What to know first

Tools you get

25 tools when we connected.

Requires

GITEE_ACCESS_TOKEN in your environment

CONTEXT COST

Moderate Standing cost

Rated by the size of the 25 tool definitions that ride along on every turn, not by how many there are

INSTALLATION

Connect your client

Server setup

go install

TERMINAL

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

Hosted endpoint

ENDPOINT URL

https://api.gitee.com/mcp

Connect a client to this instead of installing anything. Send your Gitee personal access token as an Authorization: Bearer header. Taken from this project's own documentation.

MCP Clients

Claude Code

CLAUDE CODE · JSON

{
  "mcpServers": {
    "gitee": {
      "type": "http",
      "url": "https://api.gitee.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_PERSONAL_ACCESS_TOKEN>"
      }
    }
  }
}

Codex

CODEX · TERMINAL

codex mcp add gitee --url https://api.gitee.com/mcp --bearer-token-env-var GITEE_ACCESS_TOKEN

Cursor, Trae, Continue

JSON

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

Cline

CLINE · JSON

{
  "mcpServers": {
    "gitee": {
      "type": "streamableHttp",
      "url": "https://api.gitee.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_PERSONAL_ACCESS_TOKEN>"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

OpenCode

OPENCODE · JSON

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

Gitee

The issue-to-merge loop, closed inside the editor.

What it is

What you get

Requirements

Setup effort

Turning an issue into a merged change

Reviewing a pull request you did not write

Finding where something is implemented in an unfamiliar repository

Catching up on what needs your attention

Cutting a release

Starting a new project on Gitee

25 tools

compare_branches_tags

create_comment

create_issue

create_pull

create_release

create_repo

fork_repository

get_diff_files

get_file_content

get_pull_detail

get_repo_issue_detail

get_user_info

list_comments

list_releases

list_repo_issues

list_repo_pulls

list_user_notifications

list_user_repos

manage_pull_review

merge_pull

search_files_by_content

search_open_source_repositories

search_users

update_issue

update_pull

What to know first

Tools you get

Requires

Moderate Standing cost

Connect your client

Server setup

go install

Hosted endpoint

MCP Clients

Claude Code

Codex

Cursor, Trae, Continue

Cline

OpenCode

Same category

GitHub MCP Server by MissionSquad

GitHub MCP Server by golwalak

GitHub PR & Issue Analyser

Bitbucket MCP Server

`compare_branches_tags`

`create_comment`

`create_issue`

`create_pull`

`create_release`

`create_repo`

`fork_repository`

`get_diff_files`

`get_file_content`

`get_pull_detail`

`get_repo_issue_detail`

`get_user_info`

`list_comments`

`list_releases`

`list_repo_issues`

`list_repo_pulls`

`list_user_notifications`

`list_user_repos`

`manage_pull_review`

`merge_pull`

`search_files_by_content`

`search_open_source_repositories`

`search_users`

`update_issue`

`update_pull`