How do I find my Gitee Personal Access Token?

Log in to Gitee, go to [Settings -> Personal Access Tokens](https://gitee.com/profile/personal_access_tokens), and click 'Generate new token'. Make sure to copy it immediately as it won't be shown again.

Can I read the content of a file in a private repository?

Yes, as long as your Personal Access Token has the necessary permissions (scopes) to access your private repositories, the `get_file_content` tool will work perfectly.

Is it possible to filter issues by their state?

Yes. When using `list_repo_issues`, you can provide an optional `state` parameter (e.g., 'open', 'closed', or 'all') to filter the results according to your needs.

Gitee MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Gitee
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Gitee through Vinkius, pass the Edge URL in the `mcps` parameter and every Gitee tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Gitee Specialist",
    goal="Help users interact with Gitee effectively",
    backstory=(
        "You are an expert at leveraging Gitee tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Gitee "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Gitee MCP Server

Empower your AI agent to manage your development workflow on Gitee, the leading platform for collaborative software development in China. By connecting Gitee to your agent, you transform repository management and issue tracking into a natural conversation. Your agent can instantly list your repositories, create new issues, manage pull requests, and even read file contents without you needing to navigate the web interface. Whether you are a solo developer or part of a large team, your agent acts as a real-time development assistant, keeping your projects organized and moving forward.

When paired with CrewAI, Gitee becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Gitee tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Repository Management — List all your repositories, get detailed info, and create new projects instantly.
Issue Tracking — List, filter, and create issues to keep your tasks organized and track bugs efficiently.
Pull Requests — Monitor and create pull requests to streamline your code review and merging process.
Code Access — Retrieve file contents and directory structures to understand your codebase better.
Commit History — Browse commit logs and audit changes across your branches and repositories.

The Gitee MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Gitee to CrewAI via MCP

Follow these steps to integrate the Gitee MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Gitee

Why Use CrewAI with the Gitee MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Gitee through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Gitee + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Gitee MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Gitee for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Gitee, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Gitee tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Gitee against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Gitee MCP Tools for CrewAI (10)

These 10 tools become available when you connect Gitee to CrewAI via MCP:

create_issue

Create an issue

create_pull_request

Create a pull request

create_repo

Create a new repository

get_file_content

Get file content

get_repo

Get repository details

get_user

Get authenticated user profile

list_pull_requests

List pull requests

list_repo_commits

List repository commits

list_repo_issues

List repository issues

list_user_repos

List authenticated user repositories

Example Prompts for Gitee in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Gitee immediately.

"List all my repositories on Gitee."

"Create a new issue in 'my-org/my-repo' titled 'Bug: login failure'."

"Read the contents of README.md from the main branch of 'user/project'."

Troubleshooting Gitee MCP Server with CrewAI

Common issues when connecting Gitee to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Gitee + CrewAI FAQ

Common questions about integrating Gitee MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.