Gitee MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Gitee MCP Server?

Gitee MCP Server is a tool that allows users to automate operations on Gitee repositories, issues, and pull requests using AI through the Model Context Protocol (MCP).

how to use Gitee MCP Server?

To use Gitee MCP Server, you can install it via Smithery or run it using Docker. You need to configure it with your Gitee personal access token and optionally set the Gitee API base URL.

key features of Gitee MCP Server?

  • Create, fork, and manage Gitee repositories
  • Create and update branches
  • Manage files within repositories
  • Create and comment on issues
  • Create and manage pull requests
  • Retrieve user information from Gitee

use cases of Gitee MCP Server?

  1. Automating repository management tasks in Gitee.
  2. Streamlining issue tracking and resolution processes.
  3. Facilitating collaborative development through automated pull request management.

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 open source?

Yes, it is licensed under the MIT License, allowing free use and modification.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

16 hours ago
Voyei

6 hours ago