Gitee MCP. Manage Code, Issues, and PRs via Conversation
Gitee MCP gives your AI client full command over your collaborative code base. Stop clicking through web interfaces to manage repos, track bugs, or review pull requests. This connector lets you ask natural language questions—like 'What commits were made on the staging branch last week?' or 'Create a new issue for this broken login flow'—and get instant, actionable data back from Gitee.
Give Claude and any AI agent real-world access
The agent can list all your user repositories, get detailed project information, and create entirely new ones.
You can view lists of repository issues or create a new issue to track bugs without leaving your workspace.
The system monitors pull requests for review and allows you to initiate the creation of a new pull request directly from your prompt.
You can retrieve comprehensive lists of commit logs or read specific file contents using just descriptive language.
Ask an AI about this
Waiting for input…
What AI agents can do with Gitee: 10 Tools for Code Development
Use these tools to interact with every core function of Gitee, allowing your AI client to perform actions like creating issues or listing commits directly.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Gitee MCPGet User
Retrieves the profile information for the authenticated user on Gitee.
List Pull Requests
Shows a list of existing pull requests associated with repositories.
List Repo Commits
Provides a log detailing commits made within a specific repository.
List Repo Issues
Generates a list of bugs or feature requests logged for a repository.
List User Repos
Lists all repositories owned by the currently authenticated user account.
Create Issue
Creates and logs a brand new issue detailing a problem or suggestion in a repository.
Create Pull Request
Initiates a pull request to merge changes between branches.
Create Repo
Creates an entirely new, blank repository account on Gitee.
Get File Content
Fetches and reads the actual text content of a specified file path in a repository.
Get Repo
Retrieves general structural details about a specific repository.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Gitee, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Gitee. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The friction comes from context switching.
Right now, updating your project status is a multi-step chore. You have to log into Gitee, check the 'Issues' tab for bugs, then switch over to the 'Commits' tab to see when someone fixed it, and finally jump to 'Pull Requests' to make sure the fix didn't break anything else. It’s clicking, copying, pasting, and mentally tracking where you left off.
With this MCP, that entire process collapses into a single dialogue. You ask your agent about the bug, and in one response, it synthesizes data from issues, commit logs, and pull requests. You get an immediate, coherent answer without ever leaving your chat window.
Gitee MCP gives you conversational repository control.
The manual steps that vanish are the repeated logins, the navigating between tabs (Issues -> Commits -> PRs), and the need to copy a repo name just for an API call. Your agent handles all of that under the hood.
It's not just about listing things; it's about receiving synthesized knowledge immediately. You finally get to treat your entire development stack like one conversation.
What Gitee MCP does for your AI
Dealing with large codebases means jumping between tabs: checking repo status here, opening an issue tracker there, and finally reviewing pull requests somewhere else. That friction slows you down.
This MCP connects your AI client directly to Gitee's core functions. Instead of navigating the web interface, you talk to your agent. Your agent reads repository data, lists all projects belonging to a user, and even generates new repositories on demand. Need to track something? You can list existing issues or create brand-new ones with just a prompt.
When code changes, you don't have to manually audit the history; your agent pulls commit logs and details for specific files right into your conversation. This ability to treat complex development processes like a natural dialogue makes managing dev workflows simple. It’s exactly what Vinkius built this catalog for: giving power users direct access to deep service functionality through conversational AI.
019d8440-64ce-713c-af21-9d08b43dc3af How to set up Gitee MCP
The bottom line is you use natural language commands through your agent rather than clicking buttons in a web dashboard.
Subscribe to this MCP and provide your Gitee Personal Access Token (PAT) within Vinkius.
Connect your preferred agent, like Cursor or Claude, to the Vinkius platform.
Ask your AI client to perform a development task—for example, 'List all repos for me' or 'Create an issue detailing X bug.' — and get the result instantly.
Who uses Gitee MCP
Anyone who spends more time managing development processes than actually writing code. This MCP solves the pain of context switching and navigating dozens of tabs to complete simple tasks.
Uses this to list user repositories, retrieve file contents for debugging a specific module, or quickly create an issue when they hit a roadblock.
Leverages it to monitor pull requests and audit issues across multiple projects without needing permission to log into every single repository dashboard.
Uses it to integrate Gitee data into automated workflows, checking commit history or creating new repositories as part of deployment routines.
Benefits of connecting Gitee MCP
Instead of jumping to the issue tracker page, simply ask your agent to list repository issues or create a new one. This makes bug reporting immediate and contextual.
You can perform advanced code audits without opening multiple tabs. Just prompt for commit logs or file contents; the data appears instantly in your chat window.
Need a new project? Use the tool that creates repositories so you don't have to manually navigate the creation forms on the web platform.
Reviewing code changes is faster than ever. The ability to list pull requests means you can check status and initiate reviews without leaving your development environment.
This MCP lets you manage everything from listing user repositories to getting detailed repo information, giving you a single pane of glass for all your projects.
Gitee MCP use cases
The onboarding developer needs project context
A new dev asks their agent: 'What's the current state of the payment module?' The agent calls get_repo and then gets_file_content for key files, summarizing which parts need attention. They didn't have to read a massive README file.
The PM needs to track down legacy bugs
A manager asks the agent: 'Show me all issues related to user authentication created last quarter.' The agent uses list_repo_issues, filters by date/label, and presents a clear report without needing manual filtering.
The team needs to propose a new feature
A developer prompts: 'I need a place for the new reporting tool code.' The agent uses create_repo, generating the necessary project structure instantly and providing the link.
The core dev is merging changes and needs to review them
Instead of manually opening the PR list, they ask: 'List all open pull requests for the main branch.' The agent calls list_pull_requests, giving an immediate status overview.
Gitee MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Trying to view a file's content
Manually navigating to the 'src/utils' folder in the web UI and then clicking into a specific README file just to copy text.
Just tell your agent: 'Get the file content for src/utils/README.md.' The tool handles the pathing, saving you multiple clicks.
Creating a new project
Logging into Gitee's main page and clicking through three different menus to find the 'New Repository' button.
Tell your agent: 'Create a repo called inventory-service.' It uses create_repo immediately.
Tracking down bug details
Searching for an issue using the keyword in the web search bar, only to find 50 irrelevant results that require manual sifting.
Tell your agent: 'List all open issues related to checkout payments.' The tool uses list_repo_issues and provides a focused, actionable list.
When to use Gitee MCP
Use this MCP if your workflow relies on synthesizing information across multiple development areas—like cross-referencing commit logs with current repository issues. It's best for developers who operate conversationally and need deep access to code history or project structure details.
Don't use it if you just need a simple webhook trigger (e.g., 'When X happens, send an email'). For those limited triggers, a direct API integration might be cleaner. However, if your goal is information retrieval and action based on that retrieved data, this MCP is perfect because it turns the entire platform into a conversational source of truth. If you're only listing repositories without needing details or actions (like creating issues), you can use simpler category tools, but this provides the full lifecycle management.
Frequently asked questions about Gitee MCP
How do I list my user repositories using Gitee MCP? +
You simply ask your agent to list all user repositories. The system runs the list_user_repos tool and returns a comprehensive list of every project you own.
Can I create an issue in Gitee via the Gitee MCP? +
Yes, you can. Just ask your agent to 'Create a new issue' in a specific repository, detailing the title and body content for bug tracking.
What if I need to see old code history with Gitee MCP? +
You prompt the agent to list repository commits. It executes list_repo_commits, showing you a detailed log of changes across your specified branches and projects.
Does Gitee MCP help me review pull requests? +
Yes, you can use list_pull_requests to see the status of open or closed PRs. You can even ask the agent to create a new pull request for merging code.
Is Gitee MCP only for large teams? +
No. While it's powerful for teams, solo developers use it constantly too. It lets you list your own repositories and manage personal projects just as easily.