MCP 助手
- 作者仓库星标 47,548
- 作者更新于 实时读取
- 作者仓库 metabase
- 领域
- AI 智能
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @metabase · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明（默认跨平台）
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
---
name: playwright-mcp-metabase
description: Drive Metabase's UI with the Playwright MCP browser tools (mcp__playwright__browser_*). Covers t…
category: AI 智能
runtime: 无特殊运行时
---
# playwright-mcp-metabase 输出预览
## PART A: 任务判断
- 适用问题：提示词、Agent 工作流、模型评估或自动化推理。
- 输入要求：目标材料、限制条件、期望输出和验收方式。
- 证据边界：围绕“Core pattern: Snapshot → Act → Check / How to interact with Metabase's UI components / Login”读取原文规则，不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断：确认你的需求是否属于提示词、Agent 工作流、模型评估或自动化推理，并标出输入、限制和预期结果。
- **02** 执行计划：优先按“Core pattern: Snapshot → Act → Check / How to interact with Metabase's UI components / Login”拆成步骤，说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果：给出可复制的命令、文件改动、检查清单或内容草稿，并说明如何继续迭代。
- **04** 风险边界：结合 读取文件、写入/修改文件、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件；主要在本地完成；通常不需要额外 API Key。
- 先小样例验证，再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。原文出现了 `/api` 这类斜杠命令；如果你的 Agent 支持命令触发，优先用命令开场，再补充目标和边界。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是：读取文件、写入/修改文件。
先用一个小任务确认它会围绕“Core pattern: Snapshot → Act → Check / How to interact with Metabase's UI components / Login”工作；涉及文件或命令时，先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作；如果输出泛泛而谈，就补充输入、边界和验收标准后重跑。
---
name: playwright-mcp-metabase
description: Drive Metabase's UI with the Playwright MCP browser tools (mcp__playwright__browser_*). Covers t…
category: AI 智能
source: metabase/metabase
---
# playwright-mcp-metabase
## 什么时候使用
- 把AI / Agent方向的常用动作沉淀成 Agent 可调用的技能 适合处理AI Agent、提示词、模型评估与自动化推理，核心价值是把输入、判断、执行、验证和交付边界固定下来，避免 Agent 泛泛回答。 把任务拆成可执行、可检查…
- 面向提示词、Agent 工作流、模型评估或自动化推理，优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Core pattern: Snapshot → Act → Check / How to interact with Metabase's UI components / Login」组织步骤，不把推断写成作者事实。
- 读取文件、写入/修改文件；主要在本地完成；通常不需要额外 API Key。
- 先跑小样例，确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown，不编造命令、平台或依赖。作者原文负责流程事实；仓库文件负责来源和命令；流狐只补充适用场景、限制和质量判断。
skill "playwright-mcp-metabase" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Core pattern: Snapshot → Act → Check / How to interact with Metabase's UI components / Login
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
}Browser Automation with Playwright MCP (Metabase)
A Playwright MCP server is configured in .mcp.json. Load the tool schemas first with ToolSearch: select:mcp__playwright__browser_navigate,mcp__playwright__browser_snapshot,mcp__playwright__browser_click,mcp__playwright__browser_fill,mcp__playwright__browser_type,mcp__playwright__browser_press_key,mcp__playwright__browser_hover,mcp__playwright__browser_take_screenshot,mcp__playwright__browser_close
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
browser_snapshot— see what's on screen, get element refs- Act —
browser_click,browser_fill,browser_type, etc. using refs from the snapshot - Check the inline response — every action returns a snapshot in its response. Read it.
When to take a separate browser_snapshot 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 (
browser_take_screenshotshows 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 browser_click. The hover-before-click pattern is only needed for specific component types.
Regular buttons, links, form inputs, checkboxes, tabs:
Just browser_click them directly. No hover needed.
Buttons that open dropdown menus (e.g., "+ New", "..." action menus, filter type pickers):
These use Mantine's <Menu> component which has a race condition with direct clicks. Hover before clicking these:
browser_hoveron the buttonbrowser_clickon the button- Check the inline response — if the menu appeared, use its refs directly
How to tell if a button opens a dropdown menu: it usually has a chevron/arrow icon, a "..." label, or is labeled as creating something new (like "+ New"). If unsure, try a direct click first — if it doesn't work, retry with hover.
Select and dropdown components (e.g., database picker, column picker):
Mantine Select/MultiSelect are NOT native <select> elements. browser_select_option will NOT work. Instead:
browser_clickon the input/triggerbrowser_clickon the option you want (use refs from the inline response)
You can also type into the input to filter options before clicking.
Modals and dialogs:
To dismiss: browser_click the close/action button, or browser_press_key with Escape.
⚠️ Mantine Escape-inside-modal trap: Pressing Escape while focus is inside a Mantine popover/Select/MultiSelect that is itself nested in a modal closes the entire modal and discards every form field you've already filled. To dismiss just an open dropdown, prefer browser_click outside the dropdown (or click another field). Only press Escape when you actually want the whole modal gone.
Mantine portals + scoped snapshots: Mantine renders dropdowns, popovers, and tooltips into a portal at <body> level — they are NOT children of the [role=dialog] element. If you scope browser_snapshot to the modal, dropdown options will be missing. Take a full-page snapshot when interacting with portaled content.
Login
browser_navigatetohttp://localhost:$MB_JETTY_PORT/auth/loginbrowser_snapshot→browser_fillemail and password →browser_clicksign-in buttonbrowser_navigatetohttp://localhost:$MB_JETTY_PORT/— always navigate explicitly to the home page after login. Do NOT rely on the login redirect alone. The redirect can leave the browser session in a state where clicks don't register.browser_snapshotto confirm you're logged in
Quick login via API (alternative)
Get a session token via API and set it as a cookie — faster than filling the login form:
./bin/mage -bot-api-call /api/session --method POST --body '{"username":"<email>","password":"<password>"}'Extract the id from the response, then use browser_evaluate with script:
document.cookie = 'metabase.SESSION=<token>;path=/'Then browser_navigate to the target page. Use the credentials from ./bin/mage -bot-server-info.
When clicks don't work
- Take a fresh snapshot (async rendering). 2. Try hover + click (menu triggers). 3. Try keyboard (focus + Enter). 4. After 3 attempts, report and move on.
Rules
- Always use
http://localhost:$MB_JETTY_PORT - Close the browser when done
- Use inline response snapshots when sufficient — only take separate
browser_snapshotwhen needed - Browser is pre-configured: 1440x900 viewport, full snapshot mode, isolated session, 10s action timeout
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核