Can my agent list all issues in a Gitea repository?

Yes. Use the 'list_issues' tool. Provide the owner and repository name. The agent will return all issues with their titles, numbers, states, and labels, allowing you to monitor project progress natively.

How do I check the details of a specific pull request via chat?

Use the 'list_pulls' tool to see active PRs and their numbers. You can then ask for details about a specific PR to verify source/target branches and current review status synchronously.

Can I see all repositories belonging to a Gitea organization through the agent?

Absolutely. Use the 'list_org_repos' tool. Provide the organization name, and the agent will return all repositories belonging to that org, including their clone URLs and visibility status natively.

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

Name: Gitea
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Gitea through Vinkius, pass the Edge URL in the `mcps` parameter and every Gitea 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="Gitea Specialist",
    goal="Help users interact with Gitea effectively",
    backstory=(
        "You are an expert at leveraging Gitea 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 Gitea "
        "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 Gitea MCP Server

Connect your Gitea instance to any AI agent and take full control of your self-hosted Git services, code reviews, and project collaboration through natural conversation.

When paired with CrewAI, Gitea becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Gitea 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 Orchestration — List all accessible repositories and retrieve full details including descriptions, clone URLs, stars, and visibility states natively
Issue & Task Tracking — Enumerate issues in any repository to track numbers, states, labels, and assignees, and retrieve full body content for detailed analysis flawlessly
Pull Request Auditing — List all pull requests to monitor open, closed, or merged states and review source/target branch mappings synchronously
Organization Management — Identify organizations you belong to and retrieve detailed org metadata including website, location, and repository counts securely
Branch & Protection Oversight — List all branches in a repository and verify commit SHAs and effective branch protection rules natively
User Profile Discovery — Extract the authenticated profile identity including login, email, full name, and administrative status flawlessy
Project Navigation — Analyze specific localized variables decoding active data routes and extracting hidden structural constraints within your Gitea environment

The Gitea 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 Gitea to CrewAI via MCP

Follow these steps to integrate the Gitea 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 Gitea

Why Use CrewAI with the Gitea MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Gitea 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

Gitea + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Gitea 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 Gitea, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Gitea 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 Gitea against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Gitea MCP Tools for CrewAI (10)

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

get_issue

Get full details of a Gitea issue

get_me

Get the authenticated Gitea user profile

get_org

Get full details of a Gitea organization

get_repo

Get full details of a Gitea repository

list_branches

List all branches in a Gitea repository

list_issues

List all issues in a Gitea repository

list_org_repos

List all repositories belonging to a Gitea organization

list_orgs

List all organizations the authenticated Gitea user belongs to

list_pulls

List all pull requests in a Gitea repository

list_repos

Returns repo full names, descriptions, clone URLs, stars, forks, private/public status, and default branches. List all repositories accessible to the authenticated Gitea user

Example Prompts for Gitea in CrewAI

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

"List the last 5 repositories I worked on"

"Show me open pull requests for repo 'api-service'"

"List all issues in organization 'Eng-Team'"

Troubleshooting Gitea MCP Server with CrewAI

Common issues when connecting Gitea 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.

Gitea + CrewAI FAQ

Common questions about integrating Gitea 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.