Refcat

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 聊天与邮件
• 你需要填写：Authorization

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

claude mcp add --transport http refcat https://mcp.refcat.app/mcp --header 'Authorization: your-value'

{
  "mcpServers": {
    "refcat": {
      "url": "https://mcp.refcat.app/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "servers": {
    "refcat": {
      "type": "http",
      "url": "https://mcp.refcat.app/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

• Authorization 机密 必填 HTTP header
  Bearer from refcat.app/dashboard (free plan includes one key)

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• list_facets

  The filter vocabulary with real counts (number of flows): platform, flowIntents, uiComponents, pageType and screenPatterns. Call this before filtering search_screens or search_flows so filters are real values, not guesses. Optional query/filters narrow every count, flowIntents in

• get_screen

  One catalog screen with its image and structure. Returns an image block (look at it for color, typography and spacing) and JSON with app, flow, platform, pageType, screenPatterns, uiComponents, keyTexts, dimensions, capturedAt and `elements` (OCR text and hotspots with normalized

• search_screens_by_image

  Find catalog screens that look like your images (base64, e.g. a screenshot of the app you are building). Then call get_screen on the matches to compare. Free plans: up to 2 images and 12 results.

• search_screens

  Search individual UI screens by description, app name or site ('paywall with annual plan first', 'Spotify', 'linear.app'). Returns metadata per screen; set includeImages to also get the top screens as images (max 4, ~1-2k tokens each). Call get_screen for the full structure of on

• search_flows

  Search whole flows (ordered screen sequences) by intent, app or description. Then get_flow for the steps.

• search_emails

  Search real product emails (welcome, receipts, onboarding, re-engagement…) by description or brand. Each result is one email with its desktop and/or mobile image; when hasHtml is true, get_email_html returns the original HTML to adapt. Needs Pro.

• get_email_html

  The original HTML of one email from search_emails (tables, font fallbacks, dark mode included). Adapt it to the user's brand instead of writing email HTML from scratch. Pro, or this week's free flows.

• search_apps

  Find apps in the catalog by name, website or theme ('nubank', 'linear.app', 'meditation').

• get_app

  Metadata for one app in the catalog. Accepts an appId or a slug like 'spotify'. get_app_flows lists its flows.

• get_app_flows

  The flows of one app (onboarding, checkout, settings…) in order, with capture date. Accepts an appId or slug. Big apps have hundreds of flows: page with offset. Then get_flow for the steps of one.

• similar_apps

  Apps like this one, ranked from the app's own flow themes. Accepts an appId or slug.

• get_flow

  One flow with every step in order. Compact by default: each step has screenDocId (for get_screen), pageType, patterns, components and keyTexts. include 'elements' adds OCR/hotspot boxes per step (large: tens of thousands of tokens for a long flow); 'connections' adds step links.

• get_flow_history

  Earlier captures of the same flow (how it changed over time): capture date, screen count and up to 3 preview images each.

• similar_screens

  Screens that look like a given screen. Visual, not keyword — no quota. includeImages returns the top matches as images (max 4).

• list_categories

  The catalog's category rail for a platform, with the key list_apps filters by. Emails, games, store listings and ads have their own rails.

• list_apps

  Apps in the catalog, optionally filtered by category key (from list_categories) or platform. Platform `email` lists brands with email galleries.

• list_projects

  The caller's projects, newest first.

• get_project

  One project with its screens, positions and connections.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

• ! 注意

  作者与仓库一致

  注册中心没有列出源代码仓库，因此无法将发布者（refcat.app）与代码对应起来

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 877 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 18 个工具描述，未发现针对 AI 的隐藏指令

与“聊天与邮件”中的其他服务器比较i

• 星标数多于此分类中其他 1838 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1838 个服务器的 79% 更新
• 基础检查结果等于或优于此分类中其他 1838 个服务器的 45%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

仓库中没有找到 README