Skip to main content
Glama
maxronner

@maxronner/tea-mcp

by maxronner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @maxronner/tea-mcp

No user-submitted related servers found.

    Related Servers

    • Gitea MCP Tool

      SupenBysz
      A
      license
      B
      quality
      D
      maintenance
      Enables 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.
      22
      106 npm
      6
      MIT

    • forgejo-mcp

      openmanbo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with a Forgejo instance as an authenticated user, supporting issues, pull requests, repositories, and notifications.
      18 npm
      MIT

    • Git Workflow MCP Server

      archis17
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with local Git repositories for operations like status, commits, branching, and diffs, plus GitHub API integration for managing pull requests when authenticated.
      -

    • github-mcp

      nht-x
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with GitHub directly by fetching repository information, creating issues, and triggering repository_dispatch events through natural language.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 15 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessNo issues

    Resources