Plugin

slipstream

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.

• Published source
• Repository

Analysed

11 October 2026

Last observed

14 October 2026

About this tool

What does this mean?

Listing details come from the registries and repositories where the tool is published. They help you judge who maintains it and how active it is; they are not a safety signal.

Listed on

Claude Plugin Marketplaces

Tracked by Verune

since 10 October 2026 · 1 version observed

What the code does

What does this mean?

These are capabilities our static analysis found in the latest published version. They describe what the code can do, not whether it is malicious: many tools need shell access or the network to do their job. Use them to decide what to check before installing.

Static analysis found none of the capabilities we track, such as shell commands, network requests or file writes, in the latest version.

Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.

This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.