tea vs GitHub release tag URL shape, path discarded
tea is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑27.
tea is a plugin bundle for AI coding tools published by Simon Hartcher. No marketplace we read lists it any more. GitHub release tag URL shape, path discarded is an MCP server published by sadri-dridi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  GitHub release tag URL shape, path discarded | |
|---|---|---|
| Community marketplace deevus/tea-skills | Removed on 2026-10-27 Version: 0.1.0 Forks (GitHub): 3 Stars (GitHub): 12 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | teano longer listed · | GitHub release tag URL shape, path discarded |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 12 | 0 |
| Forks (GitHub) (differs) | 3 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (agent-observatory-sensor.nolimit-observatory.workers.dev/s/gh-rel-url/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 17 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/deevus/tea-skills | github.com/sadri-dridi/named-mcp-utilities |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 2 days ago returned HTTP 200 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of tea
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Connect AI assistants to GitHub - manage repos, issues, PRs, workflows, and git operations.
-
Manage repos, issues, pull requests, and Actions.
-
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
-
forgejo-cli
Use when managing a Forgejo or Gitea server from the terminal: issues, pull requests, repositories, file contents, labels, milestones, releases, webhooks, user settings, or any…
-
GitHub project operations with quality gates
-
Manage GitHub queues, issues, pull requests, reviews, and CI.
What each says it does
tea
Skills for Gitea/Forgejo workflows using the tea CLI
GitHub release tag URL shape, path discarded
GitHub release tag URL shape, path discarded
How to run each
tea
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
GitHub release tag URL shape, path discarded As a remote MCP server
claude mcp add --transport http gh-rel-url https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/gh-rel-url/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only GitHub release tag URL shape, path discarded has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: tea · What it can do: GitHub release tag URL shape, path discarded · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.