@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 "Install 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-mcplist 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: Gitea MCP Tool
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
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/maxronner/tea-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server