Inspo vs UI Beats

A side-by-side look at the Inspo and UI Beats MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Inspo logoInspoDeveloper Tools · Local subprocess (stdio)Real production websites for coding agents: palettes, fonts, fold autopsies and reference JSX.69GreatAuth: not declaredUI Beats logoUI BeatsDeveloper Tools · Local subprocess (stdio)MCP server for UI Beats. Let your coding agent search, read and install animated React components.49FairAuth: not declared

Verdict: choose Inspo for developer tools work as a local process; choose UI Beats for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Inspo logoChoose Inspo when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like search_screens, get_screen, get_design_system.
Explore Inspo

UI Beats logoChoose UI Beats when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
Explore UI Beats

Feature & specification comparison

Rows where the two servers differ are marked.

SpecInspo logoInspoUI Beats logoUI Beats
CategoryDeveloper ToolsDeveloper Tools
Quality signal69/100 · Great49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars904234
Directory activity 1 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools15Not listed

Tools & capabilities

Inspo tools 15

  • search_screensSearch the archive of real website screenshots. Returns screens with palette, fonts, components and image URLs.
  • get_screenFetch the full record for one screen by slug - every viewport variant, palette, fonts, tech stack, designer credit.
  • get_design_systemThe full DESIGN.md for one screen - real fonts, frequency-ranked palette, CSS variables, detected tech, colour roles, type ramp. Thin captured tokens are supplemented by a live fetch of the source; `live=false` skips that.
  • find_similarA screen's nearest design neighbours - ranked by design-similarity embeddings where available, else by macrostructure / industry / style overlap. One result per site.
  • compareCompare 2-4 captured sites across palette, typefaces, macrostructure, mode, style tags, type/spacing/radius scales and container width. Returns per-site breakdowns plus what they share - triangulates a house style from a few references.
  • find_by_colorReal sites whose extracted palette sits near a hex colour (OKLAB distance, so 'close' means the same colour family, not just the same hue). Use when a brief names a brand colour.
  • find_examples_for_macrostructureReal sites exemplifying one of the 19 named macrostructures. Call it at the macrostructure-pick step. Accepts slugs ('bento-grid') or display names ('Bento Grid').
  • list_collectionsList every editor-curated issue. Use this for thematic browsing - e.g. all 'Editorial Layouts' or 'Dark Product Pages'.
  • get_filtersEvery value the filters accept: styles, industries, macrostructures, modes, vibes, colors, page types, component types. Zero input. Call it when unsure - an out-of-vocabulary value errors.
  • get_site_pagesA site's captured pages as an ordered flow (landing → pricing → features → ...) with titles, northstars and thumbnails - how a real product sequences its pages. No arguments returns the directory of flow-capable sites. Accepts a site or screen slug.
  • find_componentsReal sites featuring a specific UI component (hero, pricing, features, cta, nav, footer, testimonial, logo-cloud, faq, stat), with a per-element crop where one exists. For copy-pasteable code use get_reference_jsx.
  • get_collectionFetch one issue by slug, including the editor's blurb and ordered screen list.
  • +3 more on the listing page

UI Beats tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Inspo

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "inspo": {
      "command": "npx",
      "args": [
        "-y",
        "inspo-mcp"
      ]
    }
  }
}

UI Beats

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "ui-beats": {
      "command": "npx",
      "args": [
        "-y",
        "shadcn@latest"
      ]
    }
  }
}

Frequently asked questions

Inspo is categorized under Developer Tools and uses a local stdio subprocess. UI Beats belongs to Developer Tools and uses a local stdio subprocess. Pick Inspo for developer tools work and UI Beats for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Inspo has no declared pricing — check the project's own site. UI Beats has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add inspo and ui-beats as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Inspo has a quality signal of 69/100 (Great) with 1 views, 0 installs and 904 GitHub stars. UI Beats has 49/100 (Fair) with 0 views, 0 installs and 234 GitHub stars.