Agent skill · software engineering · metabase
playwright-mcp-metabase
Drive Metabase's UI with the Playwright MCP browser tools (mcp__playwright__browser_*). Covers the snapshot/act/check pattern, Mantine component pitfalls (Menu race, Select/MultiSelect, the Escape-closes-modal trap, portal scoping), and Metabase-specific login flows. Use whenever a session needs to interact with the Metabase UI through Playwright MCP.
Why this skill is useful
Provides specific commands and patterns for interacting with Metabase's UI using Playwright MCP that the AI wouldn't reliably generate on its own.
What it needs
Requires playwright installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 48,568 stars on the source repository.
What this skill does
Browser Automation with Playwright MCP (Metabase) A Playwright MCP server is configured in .mcp.json. Load the tool schemas first with ToolSearch: select:mcpplaywrightbrowsernavigate,mcpplaywrightbrowsersnapshot,mcpplaywrightbrowserclick,mcpplaywrightbrowserfill,mcpplaywrightbrowsertype,mcpplaywrightbrowserpresskey,mcpplaywrightbrowserhover,mcpplaywrightbrowsertakescreenshot,mcpplaywrightbrowserclose If ToolSearch says "MCP servers still connecting," wait a few seconds and retry — the server takes a moment to start on first use. Core pattern: Snapshot → Act → Check 1. browsersnapshot — see what's on screen, get element refs 2. Act — browserclick, browserfill, browsertype, etc. using refs from the snapshot 3. Check the inline response — every action returns a snapshot in its response. Read it. When to take a separate browsersnapshot after acting: The inline response snapshot looks wrong, empty, or unchanged — take a fresh one (async rendering may not have completed) You need refs for your NEXT action — the inline snapshot's refs are valid, use them directly You're unsure if the action worked — take one more snapshot to confirm When you do NOT need a separate snapshot after acting: The inline response already shows the expected change (e.g., you clicked a link and the response shows the new page) You're about to take a screenshot anyway (browsertakescreenshot shows the current state) You're doing a chain of actions on the same form (e.g., filling multiple fields) — snapshot once at the end, not after each fill Element refs go stale after every action. Use refs from the most recent snapshot or inline response — never from an earlier one. How to interact with Metabase's UI components Metabase uses Mantine UI components. Most interactions work with a plain browserclick. The hover-before-click pattern is only needed for specific component types. Regular buttons, links, form inputs, checkboxes, tabs: Just browserclick them directly. No hover needed. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills metabase/playwright-mcp-metabase