Whoogy

com.whoogyPublished by whoogy.comOfficial publisherv0.1.0Updated Oct 28, 2026

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

VerifiedStreamable HTTPWeb executableBrowser AutomationDeveloper ToolsMedia & Design

Overview

AI-generated overview

Remote Whoogy MCP server that lets an assistant compare a Figma design against a live website and return visual and content QA reports.

What you can do
  • Start and monitor Figma-versus-live-site scans, including automatic page discovery and polling of job status
  • Review matched Figma-frame to live-URL pairs and choose which pages to compare
  • Run the visual and content comparison on selected pages and read structured findings by severity and issue type
  • Fetch side-by-side Figma versus live visual diffs for a page
  • List projects and recent scans, and check the account's remaining credit balance
  • Handle Figma files on free or rate-limited teams through a plugin ingest flow or by duplicating the file
When to use it
Useful when you want design QA of a built site against its Figma source without switching to a separate app or overlay plugin, for example checking spacing, typography, color and layout drift before a launch or on each deploy.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local install or API key. Requires a Whoogy account and OAuth sign-in and consent through Whoogy's own page. A Figma file and a live site URL are needed for scans.
Before you install
Comparisons spend Whoogy credits, one per page compared, so check the balance before running scans. The OAuth flow issues a long-lived 60-day access token with no refresh tokens. Scans read your Figma files and live sites, and the duplicate tool copies a Figma file into a Whoogy-owned team.

Installation

In SourceWeft

  1. Open Whoogy in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.whoogy%2Fwhoogy-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "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

Source: README.md at commit a0aa071

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 25, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts