Whoogy

com.whoogy由 whoogy.com 发布官方发布者v0.1.0更新于 Oct 28, 2026

Compare Figma designs against live websites and get visual + content QA reports, from inside Claude.

已验证Streamable HTTP可网页运行浏览器自动化开发者工具媒体与设计

概览

AI 生成的概览

远程 Whoogy MCP 服务器，让助手把 Figma 设计与线上网站对比，并返回视觉与内容 QA 报告。

可以做什么
  • 启动并跟踪 Figma 与线上站点的对比扫描，包括自动发现页面和轮询任务状态
  • 查看匹配好的 Figma 画板与线上 URL 配对，并选择要对比的页面
  • 对选定页面执行视觉与内容对比，读取按严重程度和问题类型分类的结构化结果
  • 获取单个页面的 Figma 与线上并排视觉差异图
  • 列出项目与近期扫描，并查询账户剩余额度
  • 针对免费或受限团队的 Figma 文件，通过插件导入流程或复制文件来处理
适用场景
适合在不想切换到独立应用或叠加插件的情况下，对已上线站点与其 Figma 源稿做设计验收，例如上线前或每次部署后检查间距、字体、颜色和布局偏差。
运行要求
通过 streamable HTTP 访问的远程 MCP 端点，无需本地安装或 API 密钥。需要 Whoogy 账户，并通过 Whoogy 自有页面完成 OAuth 登录与授权。扫描需要 Figma 文件和线上站点 URL。
安装前请注意
对比会消耗 Whoogy 额度，每对比一个页面消耗一个，运行前应先查看余额。OAuth 流程发放的是有效期 60 天、无刷新令牌的长期访问令牌。扫描会读取你的 Figma 文件和线上站点，复制工具会把 Figma 文件复制到 Whoogy 拥有的团队中。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Whoogy，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.whoogy%2Fwhoogy-mcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "whoogy": {
      "type": "http",
      "url": "https://mcp.whoogy.com/mcp"
    }
  }
}

README

Whoogy MCP Server — Figma to Website Design QA for Claude

[License: MIT] [MCP Server] [Works with Claude]

Fastest Figma-to-website design QA, powered by AI. This MCP server connects Claude to Whoogy to auto-detect pages, run automated visual regression and UI comparison scans, and deliver a full design QA report in minutes — catching spacing, typography, color, and layout drift before launch, without leaving your conversation.

What is Whoogy MCP?

Whoogy compares a Figma design against its live website and reports exactly where the build has drifted from the design — pixel-level spacing errors, wrong fonts, mismatched colors, missing sections, broken layouts. This repository is the Model Context Protocol (MCP) server that exposes that Figma vs. live-site comparison as tools Claude can call directly, so a full design QA scan runs and reports back inside your AI chat instead of a separate app or browser plugin.

If you're searching for Figma to code QA, design QA automation, visual regression testing for Figma, or a Claude MCP server for design review, this is it.

Why an MCP server instead of a Figma plugin?

Most Figma-to-live-site QA tools are overlay plugins — you open Figma, open the live site, and eyeball the difference manually, page by page. Whoogy MCP flips that:

  • Automatic page discovery — give it a Figma file and a live root URL; it matches Figma frames to live routes on its own.
  • No context switching — ask Claude to run the scan, review the report, and re-run it, all in the same conversation.
  • Structured findings, not just screenshots — every issue is categorized by severity (critical → low) and type (spacing, typography, color, layout, missing element), not just a visual diff image.
  • Minutes, not hours — a full multi-page comparison report comes back in minutes, so design QA can run on every deploy, not just before a big launch.

Connect it to Claude

This is a remote MCP server — no install, no API key to copy around. Claude authenticates you through Whoogy's own sign-in (OAuth 2.1 + PKCE), so it only ever acts on the Whoogy account you approve.

Claude.ai / Claude Desktop — Settings → Connectors → Add custom connector, then paste:

https://mcp.whoogy.com/mcp

Claude will open a Whoogy sign-in/consent page; approve it once and you're connected.

Other MCP clients (Cursor, VS Code Copilot, etc.) that support remote HTTP + OAuth connectors can point at the same URL.

What it can do

ToolWhat it does
check_creditsRemaining Whoogy credit balance on the connected account
list_projectsLists the account's Whoogy projects (a live site + Figma file pairing)
list_recent_scansRecent QA scans — jobId, live URL, Figma file, status, date
check_figma_tierChecks whether a Figma file needs the plugin-ingest flow (free/rate-limited team)
start_scanStarts comparing a Figma file against a live site; returns a jobId
get_scan_statusPolls a scan/discovery job
list_discovered_pagesLists matched Figma-frame ↔ live-URL pairs for a discovery job
run_selected_pagesRuns the actual visual + content comparison on chosen pages (spends credits)
get_reportStructured findings for a completed comparison: similarity score + issues by severity
get_visual_diffSide-by-side (Figma vs. live) image for one page
create_plugin_session / check_plugin_ingest / run_scan_from_ingestFallback flow for Figma files on a free/rate-limited team, via the Whoogy Figma plugin
duplicate_figma_fileCopies a rate-limited Figma file into a Whoogy-owned team so it can be scanned directly

Typical flow: start_scan → poll get_scan_status → list_discovered_pages → confirm with the user → run_selected_pages → poll get_scan_status → get_report → get_visual_diff.

How auth works

Claude registers itself as an OAuth client (RFC 7591) and runs a standard authorization-code + PKCE flow against this server. /authorize redirects your browser to Whoogy's own consent page; once you approve with your normal Whoogy sign-in, the long-lived Whoogy JWT that flow mints becomes the MCP access token, verbatim — there's no separate token system to manage. There are no refresh tokens: the access token is a 60-day JWT, and Claude re-runs the (fast) authorization flow once it expires.

Frequently asked questions

What does this MCP server actually compare? A Figma file (or specific frames) against a live website's rendered pages — layout, spacing, typography, color, and content, page by page.

How is this different from a pixel-overlay Figma plugin? An overlay plugin needs a human to look at each page and spot differences. This server discovers pages automatically and returns a structured, severity-ranked report Claude can read, summarize, and act on.

How long does a scan take? Discovery and comparison run as background jobs; a typical multi-page report comes back within minutes of confirming which pages to run.

Is my data shared with other users? No. Every tool call runs as your signed-in Whoogy account via OAuth — reports, credits, and projects are scoped to your account only.

Which AI assistants can use this? Any MCP client that supports remote, OAuth-authenticated HTTP servers — Claude.ai, Claude Desktop, and other MCP-compatible tools (Cursor, VS Code Copilot, etc.).

Does it cost anything to run a scan? Comparisons spend Whoogy credits (one per page compared). check_credits reports your balance before you commit to a run.

Self-hosting

This server is stateless per request (a fresh McpServer + transport per HTTP call) and talks to the main Whoogy REST API over HTTP as the signed-in user — it holds no product data of its own. It shares its OAuth-grant and device-code collections with the main Whoogy API's MongoDB, so it isn't meant to be pointed at a different backend; self-hosting only makes sense if you're running the rest of Whoogy yourself too.

bash
npm installcp .env.example .env   # fill in MONGODB_URI, JWT_SECRET, MCP_API_BASE, FRONTEND_URLnpm run dev

See .env.example for what each variable does. MCP_PUBLIC_URL must be a publicly reachable HTTPS URL for any remote client (claude.ai, etc.) to connect — plain HTTP only works for purely local testing.

Learn more

License

MIT

来源：README.md，提交 a0aa071

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v0.1.0最新Sep 25, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分