Ext Ops Panel
Open dashboard
Comparison

teamcity-cli vs io.github.valewnrt/testa

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). io.github.valewnrt/testa is an MCP server published by valewnrt. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
Marketplaceteamcity-cliio.github.valewnrt/testa
Claude Code: claude-plugins-official Listed
Version: 1.3.0
Forks (GitHub): 19
Stars (GitHub): 126
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 1.3.0
Forks (GitHub): 19
Stars (GitHub): 126
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.2
Downloads/month (npm): 272
Downloads/week (npm): 198
Forks (GitHub): 1
Stars (GitHub): 3
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

teamcity-cli vs io.github.valewnrt/testa
Factteamcity-cliio.github.valewnrt/testa
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)126 (better)3 (worse)
Forks (GitHub) (differs)19 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@valewnrt/testa-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/jetbrains/teamcity-cligithub.com/valewnrt/testa
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

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.

io.github.valewnrt/testa

In its own words, on Official MCP Registry:

Drive the iOS Simulator from an agent: read the screen, tap/type/swipe, replay flows in CI.

How to run each

teamcity-cli As a Claude Code plugin

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

io.github.valewnrt/testa As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio testa -- npx -y @valewnrt/testa-mcp

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of teamcity-cli publish no settings it asks for, so we do not compare settings.

What it can do: teamcity-cli · What it can do: io.github.valewnrt/testa · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built