Lium GPU Cloud vs Thunder Compute
Lium GPU Cloud is an MCP server published by Datura-ai. Marketplaces we read that list it: 1 (Official MCP Registry). Thunder Compute is an MCP server published by Thunder-Compute. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 |  Lium GPU Cloud |  Thunder Compute |
|---|---|---|
| Official MCP Registry | Listed Version: 0.27.2 Forks (GitHub): 3 Stars (GitHub): 7 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 13 Stars (GitHub): 34 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 | Lium GPU Cloud | Thunder Compute |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 7 (worse) | 34 (better) |
| Forks (GitHub) (differs) | 3 (worse) | 13 (better) |
| Last release (differs) | 2026-10-22 | Not published |
| Where it runs (differs) | On your machine (lium.io) | Remote server (api.thundercompute.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/datura-ai/lium | github.com/thunder-compute/thunder-cli |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-20 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
Lium GPU Cloud
Rent NVIDIA GPU pods on Lium, run commands on them and remove them, billed per second.
Thunder Compute
GPU cloud platform — create, manage, and monitor instances, snapshots, SSH keys, and billing.
How to run each
Lium GPU Cloud As a local MCP server: PyPI package
claude mcp add --env "LIUM_API_KEY=<YOUR_LIUM_API_KEY>" --transport stdio lium -- uvx --from "lium.io[mcp]" lium.io mcpRequires: LIUM_API_KEY (secret)
Thunder Compute As a remote MCP server
claude mcp add --transport http thunder-compute https://api.thundercompute.com:8443/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Thunder Compute 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 Thunder Compute publish no settings it asks for, so we do not compare settings.
What it can do: Lium GPU Cloud · What it can do: Thunder Compute · Compare two other plugins
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.