Ext Ops Panel
Open dashboard
Comparison

testdino vs teamcity-cli

testdino is a plugin bundle for AI coding tools published by TestDino. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). teamcity-cli is a plugin bundle for AI coding tools published by JetBrains. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacetestdinoteamcity-cli
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 335
Stars (GitHub): 4 658
Not marked · First seen
Listed
Version: 1.3.0
Forks (GitHub): 19
Stars (GitHub): 126
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 1.3.0
Forks (GitHub): 19
Stars (GitHub): 126
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

testdino vs teamcity-cli
Facttestdinoteamcity-cli
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)4 658 (better)126 (worse)
Forks (GitHub) (differs)335 (better)19 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.testdino.com)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)82
Licence (differs)MITNot stated
Repository (differs)github.com/anthropics/claude-plugins-communitygithub.com/jetbrains/teamcity-cli
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Responded 2 days agono remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

testdino

In its own words, on Claude Code: claude-plugins-community:

Use TestDino inside Claude Code through the hosted remote MCP server to inspect test runs, debug failing test cases, manage manual tests, and run TestDino audits.

teamcity-cli

In its own words, on Claude Code: claude-plugins-official:

Agent skill for interacting with TeamCity CI/CD using the teamcity CLI. Enables Claude to explore builds, view logs, start jobs, manage queues, agents, and more.

How to run each

testdino As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install testdino@claude-community

teamcity-cli As a Claude Code plugin

Claude Code
/plugin install teamcity-cli@claude-plugins-official

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only testdino 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: testdino · What it can do: teamcity-cli · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built