MCP server

https://wingo-ui.com/mcp

• Stateless Streamable HTTP. Clients on the 2025 protocol and on the 2026-07-28 revision both work.
• Without a key you get search, docs, design rules and the source of free items. Send Authorization: Bearer wui_… from a Pro account for Pro sources.
• Clients without remote servers use the local proxy: npx -y wingo-ui@latest mcp (stdio, reads the key saved by wingo-ui login).

In your project, one command writes the rule file and the MCP config for your agent:

npx wingo-ui@latest login
npx wingo-ui@latest agents install claude   # or codex, gemini, grok, cursor, all

The configs below read the key from the WINGO_UI_API_KEY environment variable, so it never lands in your repository. Create a key in your account (it is shown once) and export it in your shell profile.

export WINGO_UI_API_KEY=wui_...

Prefer to set it up by hand? Pick your agent:

claude mcp add --transport http wingo-ui https://wingo-ui.com/mcp --header "Authorization: Bearer $WINGO_UI_API_KEY"

{
  "mcpServers": {
    "wingo-ui": {
      "type": "http",
      "url": "https://wingo-ui.com/mcp",
      "headers": {
        "Authorization": "Bearer ${WINGO_UI_API_KEY}"
      }
    }
  }
}

• search_componentsFind components, blocks, hooks and helpers by keywords.
• list_categoriesBrowse the categories with item counts.
• get_componentPro sourceProps, parts, usage, dependencies, the install command and the source.
• get_blockPro sourceA full screen or section and the components it composes.
• get_design_rulesTokens, sizes, motion, forms, overlays and mobile rules.
• get_theme_tokensThe CSS variables for light and dark mode.
• get_install_instructionsProject setup for Next.js or Vite.
• check_updatesCompare installed items with the latest release.
• get_changelogRecent releases and their notes.
• get_account_statusWhether the key has Pro, with the links to upgrade.

There is also a build_screen prompt that walks the agent through search, rules, install and composition.

Ask your agent in plain words. It picks the tools on its own:

• Build a sign-in page with an email code and passkeys using Wingo UI.
• Add a filterable orders table to this page with Wingo UI components.
• Turn this settings form into Wingo UI fields and follow its design rules.
• Check my Wingo UI components for updates and tell me what changed.

• The server always serves the latest deployed release: components, props, rules and tokens update the moment a release ships.
• check_updates compares the versions in your wingo-ui.json with the latest release, and npx wingo-ui@latest update merges the changes into your files.
• The rule files stay short and stable. npx wingo-ui@latest agents update refreshes them when they change.

• 401 invalid_api_key: the key was revoked or mistyped. Create a new one in your account.
• Pro items come back without source: the key belongs to an account without Pro. get_account_status shows what the server sees.
• 429 rate_limited: 60 requests a minute without a key, 600 with one. The response says when to retry.
• The environment variable is not picked up: start the agent from a shell that has WINGO_UI_API_KEY, or use the stdio proxy, which reads the key saved by wingo-ui login.