uxspot MCP server

The UX reference your AI assistant can call — and now, the one that draws.

uxspot.io is a free, curated UX reference: a 203-term glossary (every term with a plain-English definition and a "why it matters"), an AI x UX tools directory, 5 interactive checklists, a 78-topic Learn UX curriculum, and Spot Check, a daily UX vocabulary game. This repository documents the remote Model Context Protocol server that exposes all of it as callable tools for Claude, Cursor, and any other MCP client.

• Endpoint: https://uxspot.io/mcp — remote, Streamable HTTP, stateless
• Landing page and live demo: uxspot.io/mcp-server
• Auth: none — no key, no account, no rate-limit signup
• Privacy: every tool is read-only over public uxspot.io content. The server never sees your project, files, or account.
• Sibling project: the uxspot Figma plugin — the same reference as a design mentor inside Figma, live on Figma Community.

Install

Claude Code

claude mcp add --transport http uxspot https://uxspot.io/mcp

Claude Desktop — Settings → Connectors → Add custom connector, with URL https://uxspot.io/mcp.

Cursor — add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "uxspot": { "url": "https://uxspot.io/mcp" }
  }
}

Gemini app (Spark) — Settings → Connected apps → add a custom app, and paste https://uxspot.io/mcp as the URL (just the URL — the JSON below is Antigravity's format, not Spark's). If a credentials step appears under Advanced, leave it empty; uxspot never asks for a key.

Gemini (Antigravity) — the IDE and CLI that replaced Gemini CLI. Add to ~/.gemini/config/mcp_config.json, then /mcp in the CLI to confirm:

{
  "mcpServers": {
    "uxspot": { "serverUrl": "https://uxspot.io/mcp" }
  }
}

Gemini Enterprise is the one Gemini door that stays closed: it requires an admin-registered OAuth connector, and uxspot is keyless by design.

Any other MCP client that supports the Streamable HTTP transport: point it at https://uxspot.io/mcp.

Tools

Every answer cites its uxspot.io source URL, so you (and your assistant) can verify it.

What an answer looks like

define_term("60-30-10") returns, verbatim:

**60-30-10 rule**
A color-proportion guideline borrowed from interior design: roughly 60% of a
screen in a dominant, usually neutral color, 30% in a secondary color, and 10%
in an accent reserved for emphasis — enough color to guide the eye without
competing for it.

**Why it matters** — Screens that feel colorful but calm almost always follow
some version of this split. Inverting it — letting the accent become the
majority — is why loud interfaces feel loud: when everything asks for
attention with color, nothing gets it.

**The numbers**
- 60% — dominant, usually neutral
- 30% — secondary, supporting surfaces
- 10% — accent, reserved for emphasis and actions

┌────────────────────────────────────┐
│                          

... [View full README on GitHub](https://github.com/dockster/uxspot-mcp#readme)