MAUI Labs plugin
Plugin and maui CLI from the .NET team: MAUI skills, runtime app automation and the DevFlow MCP server for your agent.
- 238 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The tool installs the Android SDK and JDK and creates and starts emulators.
- DevFlow sees the screen, network traffic, storage and logs of the running app.
- `maui ai init` writes files and MCP configuration into the project and the user profile.
Install
- Works in
Manual install
/plugin marketplace add dotnet/maui-labsThen `/plugin install dotnet-maui@dotnet-maui-labs`. The plugin brings the MAUI skills.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The tool installs the Android SDK and JDK and creates and starts emulators.
- DevFlow sees the screen, network traffic, storage and logs of the running app.
- `maui ai init` writes files and MCP configuration into the project and the user profile.
This is third-party code. Review the repository files before installing.
What it does
The experimental .NET MAUI Labs repository holds a marketplace of agent skills and the global `maui` tool. The `dotnet-maui` plugin bundles more than twenty skills covering accessibility, performance, custom handlers, networking with offline data, notifications, localization and migration from Xamarin.Forms. DevFlow connects the agent to a running app. Through it the agent inspects the visual tree, taps elements, takes screenshots and reads network traffic and logs, while the MCP server exposes the same abilities as tools. `maui ai init` installs skills, Copilot agent definitions and MCP settings for detected environments in one step.
Who it is for. Developers of .NET MAUI apps who debug UI and platform calls together with an agent.
Good fit when
- A page built on `CollectionView` is slow and the agent must inspect the element tree in the running app.
- A project is moving from Xamarin.Forms to MAUI.
- A machine lacks the Android SDK, JDK and emulators, and `maui doctor` diagnostics are needed.
- The project needs stable AutomationIds and accessibility checks.
Not a fit when
- You need a production tool with a support guarantee.
- The project uses a mobile framework other than .NET MAUI.
- General emulator control is enough, with no insight into app internals.
Example request
Run the app in an Android emulator, use DevFlow to find the list without an AutomationId and suggest fixes.Limitations
The packages are experimental: APIs change between releases and the .NET MAUI support policy does not cover them. The global tool installs with the `--prerelease` flag. `maui ai init` writes skill files, agent definitions and MCP settings into the project. MCP registration for Copilot CLI is user-wide, other destinations are project-scoped. The `--force` flag separately authorizes replacing existing files, and `--dry-run` shows the plan without writing.
How to disable. Remove the plugin with `/plugin uninstall dotnet-maui@dotnet-maui-labs` and the MCP entries from the environment settings. `dotnet tool uninstall -g Microsoft.Maui.Cli` removes the tool.
FAQ
How do I install the MAUI Labs skills in Claude Code?
Run `/plugin marketplace add dotnet/maui-labs`, then `/plugin install dotnet-maui@dotnet-maui-labs`. The `maui ai add skill <name> --env Claude --yes` command installs a single skill.
What is DevFlow?
A tool for automating a running app: element tree, taps, screenshots, WebView, network, profiling and logs. It also works with plain .NET apps for Android, iOS and macOS.
How does `maui ai init` differ from installing the plugin?
It installs skills, Copilot agent definitions and MCP settings together, detecting the environments on the machine. The marketplace plugin brings only skills.
Can I preview the changes before anything is written?
Yes. `--dry-run` shows the recommended setup and write scopes, and `maui ai status` reports the state of local files.
Does the repository hold anything besides skills?
Yes: Comet (an MVU framework), Go, AI Extensions, AppKit and WPF backends, Essentials.AI and testing infrastructure. For an agent only the tool and the plugin matter.
Discussion
No questions or reviews yet.
Related
PluginsReady references for an agent on Syncfusion .NET MAUI DataGrid, Scheduler, themes and licensing: 76 controls from the vendor
A Callstack plugin that shows simulators and devices beside the agent chat and lets it control the mobile app.
Buoy MCP lets an agent read a running React Native or Flutter app, tap its screen and inspect the network
A plugin and MCP server that give an agent annotations on the iOS Simulator screen: element, screen, search strings, two shots.
A skill and MCP server with a library of ready SwiftUI components and recipes so the agent builds iOS screens from tested code instead of writing them from scra
An MCP server to drive iOS and Android: simulators, emulators and real devices via accessibility trees and screenshots
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| MAUI Labs (this card) | yes | 238 | ||
| dotnet-claude-kit | no | 829 | a kit for .NET in general; MAUI Labs focuses on MAUI and the running app | |
| Mobile MCP | no | not required | 10,529 | drives devices and simulators from outside; DevFlow looks into the element tree of the MAUI app itself |
README in short
The .NET MAUI team's lab: the `maui` CLI for environment diagnostics and SDK, emulator and device management, plus a set of experimental libraries. The Agent Skills section covers the skills marketplace and the `maui ai` commands.
README badge
Original SKILL.md
--- name: maui-ui-patterns description: >- Fix MAUI UI layout, state, and automation issues. USE FOR: `CollectionView` scrolling, DataTemplate bindings, command bindings, Grid/FlexLayout sizing, binding-driven states, avoiding `ScrollView` parents, stable AutomationIds, `x:DataType`, EmptyView/loading/error states. DO NOT USE FOR: Shell routes, full accessibility, vendor-specific controls. --- # MAUI UI Patterns Use this skill when creating or reshaping a MAUI page or reusable component. Prefer readable layouts, shared resources, stable automation hooks, and explicit UI states over coordinate-based or screenshot-only UI. ## Workflow 1. Inspect the existing UI style: XAML, C# Markup, MauiReactor, or Blazor Hybrid. If the requested page/component cannot be found but the user asked for a UI pattern, still provide a self-contained snippet or create the requested file at a sensible path instead of stopping with only a clarification request. 2. Choose layout primitives based on content: - `Grid` for structured forms and dashboards.