gitea

Automate Gitea repository and issue management via gitea-mcp and tea CLI.

Updated Apr 16, 2026

Search Tags:#mcp #issues #workflows #repositories #pull-requests #gitea #tea-cli

Ready to run

npx skills add https://github.com/jason-hchsieh/marketplace --skill gitea-jason-hchsieh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gitea
Source: https://github.com/jason-hchsieh/marketplace/tree/main/plugins/gitea/skills/gitea
Command: npx skills add https://github.com/jason-hchsieh/marketplace --skill gitea-jason-hchsieh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gitea operations would benefit from a unified interface that handles repository, issue, PR, and release management across MCP and tea CLI. This skill enables orchestrated actions against Gitea-hosted repositories, reducing context switching and manual CLI work.

Core Features & Use Cases

MCP-based tooling: Access 80+ tools for repositories, issues, pull requests, releases, file operations, workflows, and more.
Tea CLI fallback: When MCP isn't available or not authenticated, perform core tasks via the tea CLI with consistent output formats.
Smart detection & guidance: Detects a Gitea remote with git remote -v and directs users to use the appropriate tooling, including explicit repo specification for non-standard remotes.

Quick Start

Check the git remote to confirm a Gitea URL, then use gitea-mcp for most tasks or switch to the tea CLI if MCP is unavailable.

Frequently Asked Questions about gitea

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Gitea repository and issue management from my development environment?▼

You can automate Gitea repository and issue management by using gitea-mcp for access to 80+ tools handling repos, issues, pull requests, and releases, or fall back to the tea CLI if MCP is unavailable.

What's the best way to manage Gitea pull requests and releases without manual CLI work?▼

The best way to manage Gitea pull requests and releases without manual CLI work is through an orchestrated MCP interface that automates these actions, reducing context switching across your Gitea-hosted repositories.

Do I need a Gitea access token to manage repositories via MCP?▼

Yes, you need a GITEA_ACCESS_TOKEN to authenticate with gitea-mcp. A GITEA_HOST variable is optional, and the tea CLI serves as a fallback path when MCP is not available or authenticated.

How does this tool handle non-Gitea git remotes when listing or updating issues?▼

It detects non-Gitea remotes by checking git remote -v and forces explicit --repo usage with the tea CLI, ensuring commands target the correct Gitea repository instead of failing on unrecognized remote URLs.

Can I use the tea CLI for Gitea workflows when MCP is not available?▼

Yes, you can use the tea CLI as a fallback to perform core Gitea workflows like creating and listing repos or issues with consistent output formats when MCP is unavailable or unauthenticated.

Why does my Gitea remote detection fail when running repository operations?▼

Gitea remote detection may fail if your git remote is not a standard Gitea URL. The tool checks git remote -v and guides you to specify the repo explicitly with --repo when non-standard remotes are detected.