Dynatrace vs tierproxy
Dynatrace is a plugin bundle for AI coding tools published by Dynatrace. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Official MCP Registry, Community GitHub marketplaces). tierproxy is an MCP server published by tierproxy. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
| Marketplace |  Dynatrace |  tierproxy |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 8.0.0 Forks (GitHub): 35 Stars (GitHub): 163 Not marked · First seen |
Not listed |
| Official MCP Registry | Listed Version: 7.0.0 Forks (GitHub): 35 Stars (GitHub): 163 Not marked · First seen |
Listed Version: 0.4.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 | Dynatrace | tierproxy |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 163 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 35 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (tierproxy) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 35 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/dynatrace/dynatrace-for-ai | github.com/tierproxy/python-sdk |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
Dynatrace
Dynatrace observability skills: DQL query patterns, application and infrastructure monitoring, log analysis, problem investigation, and incident response workflows, with the Dynatrace MCP server for live platform access.
tierproxy
Multi-provider proxy infrastructure for AI/ML. Geo, sessions, cost-aware routing, usage tools.
How to run each
Dynatrace As a Claude Code plugin
/plugin install dynatrace@claude-plugins-officialtierproxy As a local MCP server: PyPI package
claude mcp add --env "TIERPROXY_API_KEY=<YOUR_TIERPROXY_API_KEY>" --transport stdio python-sdk -- uvx --spec "tierproxy[mcp]" tierproxy tierproxy-mcpRequires: TIERPROXY_API_KEY (secret)
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 Dynatrace publish no settings it asks for, so we do not compare settings.
What it can do: Dynatrace · What it can do: tierproxy · 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 Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.