Ext Ops Panel
Open dashboard
Comparison

styx vs tierproxy

styx is a plugin bundle for AI coding tools published by timmx7. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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

Where each is published
Marketplacestyxtierproxy
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 5
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.0
Downloads/month (PyPI): 78
Downloads/week (PyPI): 22
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

styx vs tierproxy
Factstyxtierproxy
Marketplaces that list it11
Stars (GitHub) (differs)5 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (localhost/mcp)On your machine (tierproxy)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)5Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/timmx7/styxgithub.com/tierproxy/python-sdk
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)not checked yetno 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

styx

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

The MCP-native AI API gateway for developers building with LLMs. Every app using AI needs API keys, cost control, and provider flexibility — Styx gives you all three through one endpoint. Route requests to OpenAI, Anthropic, Google, or Mistral with automatic failover, track spending in real-time, and manage team access with scoped API keys. Self-hosted, open source, and manageable directly from Claude Code with /styx:setup, /styx:status, and @styx-ops.

tierproxy

In its own words, on Official MCP Registry:

Multi-provider proxy infrastructure for AI/ML. Geo, sessions, cost-aware routing, usage tools.

How to run each

styx As a Claude Code plugin

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

tierproxy As a local MCP server: PyPI package

Claude Code
claude mcp add --env "TIERPROXY_API_KEY=<YOUR_TIERPROXY_API_KEY>" --transport stdio python-sdk -- uvx --spec "tierproxy[mcp]" tierproxy tierproxy-mcp

Requires: TIERPROXY_API_KEY (secret)

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

Only styx 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

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

What it can do: styx · What it can do: tierproxy · 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 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