io.github.basalt-run/basalt vs GPTaria MCP
io.github.basalt-run/basalt is an MCP server published by basalt-run. Marketplaces we read that list it: 1 (Official MCP Registry). GPTaria MCP is an MCP server published by gptaria-mcp. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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 |  io.github.basalt-run/basalt |  GPTaria MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.2.1 Downloads/month (npm): 106 Downloads/week (npm): 35 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 | io.github.basalt-run/basalt | GPTaria MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (basalt.run/api/mcp) | On your machine (gptaria-mcp) |
| Transport (differs) | SSE | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/basalt-run/design-system | github.com/gptaria-mcp/gptaria-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 404 (14 h ago) | no 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
io.github.basalt-run/basalt
Design tokens, components, icons, and a11y data via MCP. For Cursor, Claude, and Windsurf.
GPTaria MCP
Post a project brief & publish cases on GPTaria from Claude Code, Cursor or Windsurf.
How to run each
io.github.basalt-run/basalt As a remote MCP server
claude mcp add --transport sse basalt https://basalt.run/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
GPTaria MCP As a local MCP server: npm package
claude mcp add --env "GPTARIA_API_KEY=<YOUR_GPTARIA_API_KEY>" --transport stdio gptaria-mcp -- npx -y gptaria-mcpRequires: GPTARIA_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.basalt-run/basalt 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 io.github.basalt-run/basalt publish no settings it asks for, so we do not compare settings.
What it can do: io.github.basalt-run/basalt · What it can do: GPTaria MCP · Compare two other plugins
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.