Ext Ops Panel
Open dashboard
Comparison

slipstream vs Flutter Lamp

slipstream is a plugin bundle for AI coding tools published by devoncarew. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Flutter Lamp is an MCP server published by itsonu. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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
MarketplaceslipstreamFlutter Lamp
Claude Code: claude-plugins-community Listed
Version: 1.6.0
Forks (GitHub): 0
Stars (GitHub): 5
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.21.0
Downloads/month (npm): 409
Downloads/week (npm): 47
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

slipstream vs Flutter Lamp
FactslipstreamFlutter Lamp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)5 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (flutter-lamp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)52
Licence (differs)BSD-3-ClauseMIT
Repository (differs)github.com/devoncarew/flutter-slipstreamgithub.com/itsonu/flutter-lamp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-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

slipstream

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

A tool that makes AI coding agents more effective for Dart and Flutter projects. AI agents working on Dart and Flutter run into two recurring problems. First, their training data has a cutoff — they'll reach for discontinued packages, pin outdated major versions, or produce subtly wrong API signatures that compile only after a correction loop. Second, Flutter development is inherently visual and stateful, and agents have no way to see a running app: they can't observe a layout failure, verify that a state change took effect, or confirm that a navigation worked. This tool addresses both. It adds hooks that catch stale package choices before they land in `pubspec.yaml`, an MCP server that retrieves accurate package API signatures directly from the local pub cache, and a suite of MCP commands for launching, inspecting, and interacting with a running Flutter app.

Flutter Lamp

In its own words, on Official MCP Registry:

Live runtime data from a running Flutter app: exceptions, logs, network, frames, diagnosis.

How to run each

slipstream As a Claude Code plugin

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

Flutter Lamp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio flutter-lamp -- npx -y flutter-lamp

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

Neither one's marketplaces publish the settings it asks for.

What it can do: slipstream · What it can do: Flutter Lamp · 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. 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.

Where the data comes from: how the catalog is built