Gitee MCP Server

Created By
normal-codera year ago
MCP Tool Server for Gitee, supporting the management of repository files/branches, Issues, and Pull Requests.
Overview

what is Gitee MCP Server?

Gitee MCP Server is a tool designed to automate the management of Gitee repositories, including operations on files, branches, issues, and pull requests using AI.

how to use Gitee MCP Server?

To use Gitee MCP Server, you can install it via Smithery or run it using Docker. Configuration requires a Gitee personal access token for authentication.

key features of Gitee MCP Server?

  • Create, fork, and manage repositories
  • Create and manage branches
  • Handle file operations such as creating, updating, and pushing files
  • Manage issues and pull requests with ease
  • User information retrieval

use cases of Gitee MCP Server?

  1. Automating repository management tasks in Gitee.
  2. Streamlining the process of handling issues and pull requests.
  3. Facilitating collaboration by managing branches and files efficiently.

FAQ from Gitee MCP Server?

  • What is required to run Gitee MCP Server?

You need a Gitee personal access token and Node.js installed on your machine.

  • Can I run Gitee MCP Server in a Docker container?

Yes! Gitee MCP Server can be run using Docker for easier deployment.

  • Is Gitee MCP Server free to use?

Yes, it is open-source and free to use under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
normal-coder
Star
-
Language
-
License
-

Recommend Servers

View All
Crevio

a day ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

19 hours ago