Gitee MCP Server

Created By
oschinaa year ago
mcp-gitee is a Model Context Protocol (MCP) server implementation for Gitee. It provides a set of tools that interact with Gitee's API, allowing AI assistants to manage repository, issues, pull requests, etc.
Overview

What is Gitee MCP Server?

Gitee MCP Server is a Model Context Protocol (MCP) server implementation for Gitee, designed to facilitate interaction with Gitee's API, enabling AI assistants to manage repositories, issues, pull requests, and more.

How to use Gitee MCP Server?

To use Gitee MCP Server, you need to install it by cloning the repository and building it from source or using Go install. After installation, configure it with your Gitee access token and API base URL, then run the server with the appropriate command-line options.

Key features of Gitee MCP Server?

  • Interact with Gitee repositories, issues, pull requests, and notifications.
  • Configurable API base URL to support different Gitee instances.
  • Command-line flags for easy configuration.
  • Supports personal, organization, and enterprise operations.

Use cases of Gitee MCP Server?

  1. Managing repository issues and pull requests.
  2. Automating repository management tasks for AI assistants.
  3. Integrating Gitee functionalities into other applications.

FAQ from Gitee MCP Server?

  • What are the prerequisites for using Gitee MCP Server?

You need Go 1.23.0 or higher and a Gitee account with an access token.

  • How can I configure the server?

You can configure the server using command-line options or environment variables for the Gitee access token and API base URL.

  • Is Gitee MCP Server open-source?

Yes, Gitee MCP Server is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
oschina
Star
28
Language
Go
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago