logo
Free, unlimited AI code reviews that run on commit
git-lrc git-lrc GitHub Install Now We'd appreciate a star git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt git-lrc - Free, unlimited AI code reviews that run on commit | Product Hunt

gitee-integration-adapter

Facilitates comprehensive governance over Gitee code repositories, issue tracking, collaborative pull requests, and system notifications via robust API interfacing. Enables automated operational sequences and refined collaboration pipelines through customizable parameters.

Author

gitee-integration-adapter logo

JJ-H

MIT License

Quick Info

GitHub GitHub Stars 0
NPM Weekly Downloads 30
Tools 1
Last Updated 2026-02-19

Tags

repositoriesrepositorytoolsgitee repositoriesbusiness toolsmanagement gitee

Gitee Operational Nexus Adapter

This Gitee Operational Nexus Adapter functions as a specialized Model Context Protocol (MCP) server endpoint targeting the Gitee platform. It furnishes a suite of utilities for programmatic interaction with Gitee's Application Programming Interface (API), empowering intelligent agents to administer repositories, resolve tracked items, manage code merges, and monitor updates.

Core Capabilities

  • Interface with Gitee repositories, tracked items, merge requests, and platform alerts.
  • Adaptable configuration for the API endpoint root to accommodate diverse Gitee deployments.
  • Command-line arguments facilitating straightforward configuration setup.
  • Comprehensive support for interactions spanning individual, organizational, and enterprise contexts.
Illustrative Workflow: Issue Retrieval, Implementation, and Merge Proposal Submission 1. Acquire pending tracked items associated with the repository. 2. Execute necessary code modifications derived from the tracked item specifications, subsequently proposing a merge request. 3. Append commentary to the tracked item and formally resolve/close it.

Deployment Preparation (Can be bypassed for direct execution via npx)

System Prerequisites

  • Go language runtime, version 1.23.0 or superior.
  • A valid Gitee credential set featuring an access token (Token Generation Portal).

Compilation From Source

  1. Clone the source repository: bash git clone https://gitee.com/oschina/mcp-gitee.git cd mcp-gitee

  2. Compile the application binary: bash make build

Ensure the resulting binary ./bin/mcp-gitee is available in the system's PATH environment.

Installation via Go Modules

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

Execution

Verify the installed version:

bash mcp-gitee --version

MCP Endpoint Configuration

Configuration templates: Expand for additional setup documentation

  • Via npx:

{ "mcpServers": { "gitee": { "command": "npx", "args": [ "-y", "@gitee/mcp-gitee@latest" ], "env": { "GITEE_API_BASE": "https://gitee.com/api/v5", "GITEE_ACCESS_TOKEN": "" } } } }

  • Standalone Executable:

{ "mcpServers": { "gitee": { "command": "mcp-gitee", "env": { "GITEE_API_BASE": "https://gitee.com/api/v5", "GITEE_ACCESS_TOKEN": "" } } } }

Runtime Arguments

  • -token: Credential for Gitee authentication.
  • -api-base: Specifies the primary Gitee API URL (defaults to https://gitee.com/api/v5).
  • -version: Outputs version metadata.
  • -transport: Defines the communication protocol (options: stdio or sse, default: stdio).
  • -sse-address: Network location for the Server-Sent Events listener (default: localhost:8000).

Environment Configuration Variables

You may also specify parameters using ambient system variables:

  • GITEE_ACCESS_TOKEN: Gitee authentication token.
  • GITEE_API_BASE: Gitee API base endpoint.

Licensing

This software is distributed under the terms of the MIT License. Consult the LICENSE file for complete legal text.

Toolset Inventory

The server exposes several specialized utilities for Gitee interaction:

Utility Name Functional Domain Operational Summary
list_user_repos Repository Retrieve a catalog of repositories accessible by the user.
get_file_content Repository Fetch the contents of a specified file within a repository.
create_user_repo Repository Provision a new repository under the user's account.
create_org_repo Repository Provision a new repository under an organization's scope.
create_enter_repo Repository Provision a new repository within an enterprise context.
fork_repository Repository Generate a clone (fork) of an existing repository.
create_release Repository Publish a new versioned release for a repository.
list_releases Repository Enumerate all existing releases associated with a repository.
search_open_source_repositories Repository Query the public Gitee ecosystem for open-source repositories.
list_repo_pulls Pull Request Display the active and closed merge requests for a repository.
merge_pull Pull Request Integrate the changes from a specific merge request.
create_pull Pull Request Initiate a new merge request for code integration.
update_pull Pull Request Modify the parameters of an existing merge request.
get_pull_detail Pull Request Retrieve comprehensive metadata for a merge request.
comment_pull Pull Request Attach textual annotations to a merge request.
list_pull_comments Pull Request List all comments appended to a specific merge request.
create_issue Issue Log a new tracked item/bug report.
update_issue Issue Modify the status or details of an existing tracked item.
get_repo_issue_detail Issue Fetch the complete record for a specific repository tracked item.
list_repo_issues Issue Obtain a listing of tracked items pertinent to a repository.
comment_issue Issue Add commentary to a specific tracked item.
list_issue_comments Issue View all annotations associated with a tracked item.
get_user_info User Retrieve authentication details for the currently connected user.
search_users User Perform a lookup for other Gitee users.
list_user_notifications Notification Display pending alerts and notifications for the user.

Community Engagement

Contributions from the open-source community are highly valued! To participate in the development of this tool, please adhere to the following process:

  1. Duplicate the primary repository (Fork).
  2. Establish a dedicated branch for your intended feature enhancement or defect correction.
  3. Implement modifications, ensuring all new or altered code segments are thoroughly documented.
  4. Submit a formal pull request containing a concise, clear summary of the introduced changes.

Further elaboration on contribution standards is available in the dedicated CONTRIBUTING document.

See Also

`