@maxronner/tea-mcp
Allows interaction with a Gitea instance, providing tools for managing issues (list, view, create, close, reopen), pull requests (list, view, create, checkout, approve, reject, merge), and repositories (list, view) through the tea CLI.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@maxronner/tea-mcp list open issues"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@maxronner/tea-mcp
MCP (Model Context Protocol) server for tea CLI - interact with Gitea repositories, issues, and pull requests from AI assistants.
Features
List, view, create, close, and reopen issues
List, view, and checkout pull requests
Create pull requests with preview mode - review changes before creating
Approve and reject pull requests - complete PR review workflow
Merge pull requests - with multiple merge strategies (merge, squash, rebase)
List and view repository details
Full integration with MCP-compatible AI tools
Related MCP server: Omnigit GitHub & Local Git MCP Server
Prerequisites
Node.js 18+
tea CLI installed and configured with your Gitea instance
Installation
Option 1: NPX (Recommended)
npx @maxronner/tea-mcpOption 2: Global Install
# Using npm
npm install -g @maxronner/tea-mcp
# Using bun
bun install -g @maxronner/tea-mcpOption 3: Use with MCP Client
Add to your MCP client configuration (e.g., Claude Desktop, Cline):
{
"mcpServers": {
"tea": {
"command": "npx",
"args": ["@maxronner/tea-mcp"]
}
}
}Available Tools
Issue Tools
tea_issues_list
List issues in the current repository.
Parameters:
state(optional): "open" | "closed" | "all" (default: "open")limit(optional): 1-100 (default: 30)labels(optional): Filter by labels (comma-separated)author(optional): Filter by author
tea_issue_view
View details of a specific issue.
Parameters:
index(required): Issue number
tea_issue_close
Close an issue.
Parameters:
index(required): Issue number
tea_issue_reopen
Reopen a closed issue.
Parameters:
index(required): Issue number
Pull Request Tools
tea_prs_list
List pull requests in the current repository.
Parameters:
state(optional): "open" | "closed" | "all" (default: "open")limit(optional): 1-100 (default: 30)
tea_pr_view
View details of a specific pull request.
Parameters:
index(required): Pull request number
tea_pr_checkout
Checkout a pull request locally.
Parameters:
index(required): Pull request number to checkout
tea_pr_create
Create a new pull request with optional preview mode.
Parameters:
title(required): Pull request titledescription(optional): PR body/descriptionhead(optional): Source branch name (defaults to current branch)base(optional): Target branch name (defaults to the repository default branch)preview(optional): Show diff without creating PR (default: false)assignees(optional): Comma-separated usernames to assignlabels(optional): Comma-separated labels to assignmilestone(optional): Milestone to assign
Usage:
// Preview what the PR will include
{ "title": "My Feature", "preview": true }
// Create the actual PR
{ "title": "My Feature", "description": "Adds cool feature", "base": "main" }tea_pr_approve
Approve a pull request.
Parameters:
index(required): Pull request number to approvecomment(optional): Approval comment
Example:
{ "index": 42, "comment": "LGTM! Great work." }tea_pr_reject
Request changes on a pull request.
Parameters:
index(required): Pull request number to rejectreason(required): Reason for requesting changes
Example:
{ "index": 42, "reason": "Please fix the variable naming convention" }tea_pr_merge
Merge a pull request.
Parameters:
index(required): Pull request number to mergestyle(optional): Merge strategy - "merge" | "rebase" | "squash" | "rebase-merge" (default: "merge")title(optional): Custom merge commit titlemessage(optional): Custom merge commit message
Example:
// Standard merge
{ "index": 42 }
// Squash merge with custom message
{ "index": 42, "style": "squash", "message": "Squashed feature commits" }Repository Tools
tea_repos_list
List repositories you have access to.
Parameters:
limit(optional): 1-100 (default: 30)type(optional): "fork" | "mirror" | "source"
tea_repo_view
View details of a repository.
Parameters:
repo(optional): Repository in "owner/name" format (defaults to current repo)
Development
Setup
git clone https://github.com/maxronner/tea-mcp.git
cd tea-mcp
bun installCommands
bun run build # Build TypeScript
bun test # Run tests
bun run test:run # Run tests once
bun run test:coverage # Run tests with coverage
bun run lint # Run ESLint
bun run lint:fix # Fix lint issues
bun run format # Format with Prettier
bun run typecheck # Type check without emitTesting
This project uses bun:test with mocked child process execution to test without requiring the tea CLI.
Coverage threshold: 80%
Important Notes
Self-Approval in Gitea
Gitea allows PR authors to approve their own pull requests by default. This is different from GitHub's default behavior. Here's what you need to know:
Default behavior: PR authors can approve their own PRs, and these approvals count toward any required approval count
Branch protection: To enforce proper review workflows, use branch protection rules:
Set "Required approving reviews" to a higher number (e.g., 2+) to ensure external review
Enable "Require review from Code Owners" and define a
CODEOWNERSfileConsider enabling
BlockAdminMergeOverrideto prevent even admins from bypassing rules
Recommended Branch Protection Setup
Navigate to Repository Settings → Branches → Branch Protection Rules
Enable "Require pull request reviews before merging"
Set "Required approving reviews" to at least 2
Create a
.gitea/CODEOWNERSfile:
# Default reviewers for all changes
* @team-lead @senior-devs
# Specific paths require specific reviewers
/src/**/*.ts @typescript-maintainers
/docs/** @documentation-teamEnable "Require review from Code Owners" in branch protection
This ensures proper code review even when working solo or in small teams.
Contributing
Fork the repository
Create a feature branch:
git checkout -b feature/my-featureMake your changes and ensure tests pass:
bun run test:runCommit with conventional commits
Push and create a pull request
License
MIT (c) Max Ronner
Links
Available Tools
15 toolstea_create_commentA
Add a comment to an issue or pull request
Inputs: body (required), index (required), repo.
tea_issue_closeB
Close an issue
Inputs: index (required), repo.
tea_issue_createB
Create a new issue in the current repository
Inputs: title (required), repo, labels, deadline, +4 more.
tea_issue_reopenC
Reopen a closed issue
Inputs: index (required), repo.
tea_issues_listB
List issues in the current repository
Inputs: repo, limit, state, author, +1 more.
tea_issue_viewA
View details of a specific issue
Inputs: index (required), repo.
tea_pr_approveB
Approve a pull request
Inputs: index (required), repo, comment.
tea_pr_checkoutB
Checkout a pull request locally
Inputs: index (required), repo.
tea_pr_createA
Create a new pull request with optional preview mode to review changes first
Inputs: title (required), base, head, repo, +5 more.
tea_pr_mergeB
Merge a pull request
Inputs: index (required), repo, style, title, +1 more.
tea_pr_rejectB
Request changes on a pull request
Inputs: index (required), reason (required), repo.
tea_prs_listC
List pull requests in the current repository
Inputs: repo, limit, state.
tea_pr_viewA
View details of a specific pull request
Inputs: index (required), repo.
tea_repos_listB
List repositories you have access to
Inputs: type, limit.
tea_repo_viewA
View details of a repository
Inputs: repo.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 15 tools
Each tool targets a distinct resource and action: issues have list/view/close/reopen/create, PRs have list/view/checkout/create/approve/reject/merge, plus comment creation and repo view/list. No two tools overlap in purpose.
Most tools follow a resource_action pattern (tea_issue_view, tea_pr_merge), but there are deviations: 'tea_prs_list' uses plural 'prs' while others use 'pr', and 'tea_create_comment' uses action_resource instead of resource_action.
15 tools is well-scoped for a Git hosting server covering repositories, issues, pull requests, and comments. Each tool earns its place without bloat or redundancy.
Core workflows are covered: issue lifecycle (create, view, list, close, reopen), PR lifecycle (create, view, list, merge, approve, reject, checkout), and comments. Minor gaps include lack of update/edit operations for issues and PRs, and no repo creation or deletion, but these do not cause major dead ends.
Maintenance
Related MCP Connectors
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Operate GitHub from your AI assistant: repos, PRs, issues, Actions. Previews and read-only mode.
Read and write KukGit repositories, files, issues and pull requests from an AI assistant.
Connect AI assistants to your GitHub-hosted Obsidian vault to seamlessly access, search, and analy…
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Gitea repositories through intelligent tools for issue/PR management, workflow analysis, compliance checking, and content generation, plus 200+ CLI commands for complete CRUD operations.22102 npm6MIT
- AlicenseNot gradedqualityDmaintenanceConnects AI tools to GitHub and local git repositories, enabling natural language management of issues, PRs, code analysis, and workflows.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with a Forgejo instance as an authenticated user, supporting issues, pull requests, repositories, and notifications.26 npmMIT
- AlicenseCqualityBmaintenanceEnables AI assistants to manage Forgejo repositories, issues, pull requests, files, commits, Actions workflow runs, organizations, and notifications through the Forgejo REST API using natural language.50MIT