@maxronner/tea-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tea_issues_listB | List issues in the current repository |
| tea_issue_viewA | View details of a specific issue |
| tea_issue_closeB | Close an issue |
| tea_issue_reopenC | Reopen a closed issue |
| tea_issue_createB | Create a new issue in the current repository |
| tea_create_commentA | Add a comment to an issue or pull request |
| tea_prs_listC | List pull requests in the current repository |
| tea_pr_viewA | View details of a specific pull request |
| tea_pr_checkoutB | Checkout a pull request locally |
| tea_pr_createA | Create a new pull request with optional preview mode to review changes first |
| tea_pr_approveB | Approve a pull request |
| tea_pr_rejectB | Request changes on a pull request |
| tea_pr_mergeB | Merge a pull request |
| tea_repos_listB | List repositories you have access to |
| tea_repo_viewA | View details of a repository |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.