candor-ui-docs

endpoint

https://candor.themethodic.com/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is candor-ui-docs live?

Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.

Is candor-ui-docs free to use?

Yes — the hub reached it with no key and no payment.

What tools does candor-ui-docs have?

13 tools: suggest_components, get_pattern, get_component_docs, search_docs, get_screen, get_started, get_brief, get_design, ….

Is candor-ui-docs safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• list_screens open 13h ago

  List the screen catalogue by area (talking to the agent, approving and controlling, watching the work, …), one line per screen: what it's for and its slug. Read one with get_screen.

  mcp-tool

  123456789

  {
    "type": "object",
    "properties": {
      "area": {
        "type": "string",
        "description": "An area's title, e.g. \"Watching the work\". Leave it out for every screen."
      }
    }
  }

  arguments 9 lines copy
• list_components open 13h ago

  List every item by group (Chat, Agent work, App shell, …), or one group's items with descriptions.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "properties": {
      "tier": {
        "enum": [
          "free",
          "pro",
          "premium"
        ],
        "type": "string",
        "description": "Only items this tier unlocks."
      },
      "group": {
        "type": "string",
        "description": "A group's title, e.g. \"Chat\" or \"Full-stack blocks\". Leave it out for the overview."
      }
    }
  }

  arguments 18 lines copy
• get_review_checklist open 13h ago

  The checklist to run after each screen where an AI agent acts, before moving on: one line per check, each tied to a rule (model output is text, unknown stays unknown, a locked control says why, nothing pre-selected, approve the exact change, reasoning is believed, the app names the agent, say what can be undone, plus status, progress and accessibility). From the candor-agent-ui skill; works with or without Candor.

  mcp-tool

  12345678910

  {
    "type": "object",
    "properties": {
      "version": {
        "type": "string",
        "maxLength": 32,
        "description": "A release, e.g. \"2.6.2\": the page as that release published it, for a project that has that version installed. Default: the version the server's URL passes (`?kit=`, which `npx candor-ui mcp` writes from candor-lock.json), else the current docs. When that release's docs weren't kept, or the page isn't in them, the answer is the current page with a note saying so."
      }
    }
  }

  arguments 10 lines copy
• suggest_components unknown never probed

  Describe the screen or feature you're building; get the Candor UI items that fit, why, the matching patterns and screens, and an install command per tier. When nothing in Candor fits, it says so rather than suggesting something close. Pass `sdk` so only your agent SDK's adapter is suggested. Read each suggestion's docs before using it.

  mcp-tool

  123456789101112131415161718192021222324252627282930

  {
    "type": "object",
    "required": [
      "task"
    ],
    "properties": {
      "sdk": {
        "enum": [
          "ai-sdk",
          "claude",
          "ag-ui"
        ],
        "type": "string",
        "description": "The agent SDK the app uses: ai-sdk (the Vercel AI SDK), claude (the Claude Agent SDK) or ag-ui. Only that SDK's adapter and block versions are suggested. Leave it out and no adapter is installed; the answer says which to add."
      },
      "task": {
        "type": "string",
        "description": "What you're building, e.g. \"a chat where the agent asks before deploying\"."
      },
      "tier": {
        "enum": [
          "free",
          "pro",
          "premium"
        ],
        "type": "string",
        "description": "Only suggest what this tier unlocks. Leave it out to see everything, with tiers marked."
      }
    }
  }

  arguments 30 lines copy
• get_pattern unknown never probed

  Read a pattern as Markdown: a common problem in agent UIs (approvals, traces, cost guards, …) and the components that solve it.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "The pattern's slug, as search_docs or suggest_components gives it."
      },
      "version": {
        "type": "string",
        "maxLength": 32,
        "description": "A release, e.g. \"2.6.2\": the page as that release published it, for a project that has that version installed. Default: the version the server's URL passes (`?kit=`, which `npx candor-ui mcp` writes from candor-lock.json), else the current docs. When that release's docs weren't kept, or the page isn't in them, the answer is the current page with a note saying so."
      }
    }
  }

  arguments 17 lines copy
• get_component_docs unknown never probed

  Read one item's docs as Markdown: what it is, its tier and install command, an example with the import paths an app uses, every prop, function, type, and the LocaleProvider string keys.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "The registry name, e.g. \"thread\", \"approval-request\" or \"cost-guard-claude\"."
      },
      "version": {
        "type": "string",
        "maxLength": 32,
        "description": "A release, e.g. \"2.6.2\": the page as that release published it, for a project that has that version installed. Default: the version the server's URL passes (`?kit=`, which `npx candor-ui mcp` writes from candor-lock.json), else the current docs. When that release's docs weren't kept, or the page isn't in them, the answer is the current page with a note saying so."
      }
    }
  }

  arguments 17 lines copy
• search_docs unknown never probed

  Search Candor UI's components, hooks, blocks and patterns by what they do ("approve a tool call", "cost estimate", "session list"). Returns names, tiers and one-line descriptions; read one with get_component_docs.

  mcp-tool

  123456789101112131415161718192021222324252627

  {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "tier": {
        "enum": [
          "free",
          "pro",
          "premium"
        ],
        "type": "string",
        "description": "Only items this tier unlocks: free, pro (free and Pro) or premium (everything)."
      },
      "limit": {
        "type": "integer",
        "maximum": 25,
        "minimum": 1,
        "description": "At most this many items (default 10)."
      },
      "query": {
        "type": "string",
        "description": "What you're looking for, in words."
      }
    }
  }

  arguments 27 lines copy
• get_screen unknown never probed

  Read one screen as Markdown: what it's for, two or three layouts with when to pick each, the Candor UI items that build each (with tiers), an install command, the honesty rules that matter most on it, and a brief to hand to the coding agent that builds it.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "description": "The screen's slug, as list_screens or suggest_components gives it, e.g. \"approvals-inbox\"."
      },
      "version": {
        "type": "string",
        "maxLength": 32,
        "description": "A release, e.g. \"2.6.2\": the page as that release published it, for a project that has that version installed. Default: the version the server's URL passes (`?kit=`, which `npx candor-ui mcp` writes from candor-lock.json), else the current docs. When that release's docs weren't kept, or the page isn't in them, the answer is the current page with a note saying so."
      }
    }
  }

  arguments 17 lines copy
• get_started unknown never probed

  How to install Candor UI in a React or Next.js app, render a chat, connect an agent SDK, add licensed items and keep them updated. With `prompt: true`, only "Give this to your agent": one block of text for adopting Candor into an app that already exists (it asks about the stack and the agent's API first, installs with the CLI, leaves the licence key to the person and names the providers to wrap the app in).

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "properties": {
      "prompt": {
        "type": "boolean",
        "description": "true: only the adoption prompt, to hand to a coding agent."
      },
      "version": {
        "type": "string",
        "maxLength": 32,
        "description": "A release, e.g. \"2.6.2\": the page as that release published it, for a project that has that version installed. Default: the version the server's URL passes (`?kit=`, which `npx candor-ui mcp` writes from candor-lock.json), else the current docs. When that release's docs weren't kept, or the page isn't in them, the answer is the current page with a note saying so."
      }
    }
  }

  arguments 14 lines copy
• get_brief unknown 2d ago

  One item's brief to hand to the coding agent that builds the screen: the same Markdown the docs page's "Copy for a coding agent" button copies (what the item is, its tier and install command, an example with the import paths an app uses, every prop, the string keys, and the rules to keep).

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "The registry name, e.g. \"thread\" or \"approval-request\"."
      },
      "version": {
        "type": "string",
        "maxLength": 32,
        "description": "A release, e.g. \"2.6.2\": the page as that release published it, for a project that has that version installed. Default: the version the server's URL passes (`?kit=`, which `npx candor-ui mcp` writes from candor-lock.json), else the current docs. When that release's docs weren't kept, or the page isn't in them, the answer is the current page with a note saying so."
      }
    }
  }

  arguments 17 lines copy
• get_design unknown never probed

  The design system as Markdown: every colour role and what it's for, the type scale, radius, shadows, motion, density and themes, read from the shipped CSS; how an app re-tokens for its brand; and how to build the screens around Candor components (surfaces, rhythm, writing, do and don't).

  mcp-tool

  12345678910

  {
    "type": "object",
    "properties": {
      "version": {
        "type": "string",
        "maxLength": 32,
        "description": "A release, e.g. \"2.6.2\": the page as that release published it, for a project that has that version installed. Default: the version the server's URL passes (`?kit=`, which `npx candor-ui mcp` writes from candor-lock.json), else the current docs. When that release's docs weren't kept, or the page isn't in them, the answer is the current page with a note saying so."
      }
    }
  }

  arguments 10 lines copy
• theme_check unknown never probed

  Check a brand file (candor-brand.css, or any CSS that sets Candor's tokens) the way `npx candor-ui theme check` does: colour contrast of every text and edge pairing in light, dark and high contrast, each with its ratio and the ratio it needs; then the --cd-motion-* and --cd-sound-* values against the motion manifest; then token names and data-slot selectors against the token manifest, as warnings that don't fail the check (a --cd-* name the kit doesn't read, with the nearest one it does; a value outside a token's range; an internal --cd-* name a brand file shouldn't set; a [data-slot] selector no component renders). Call it with the file's contents after you edit candor-brand.css, and fix what it reports before you say the theme is done. Returns a short summary (failures first, with a suggested lightness that would pass; findings with file, line and the fix), then the findings as JSON (ok, motionChecked, counts, themes with every pairing, suggestions, motionAndSound.findings, tokens.findings). Anything it can't read (a color-mix(), a var(), a sound file) is reported as not measured, never as a pass. Sound files are not measured here: the server can't see your public/ folder, so `npx candor-ui theme check` in the project does that. It checks against the current kit; an older @candor-kit in the file is checked against the current names, with a note. It reads only the CSS you send, follows no @import and fetches nothing. At most 256 KB. Example arguments: { "css": ":root { --primary: oklch(0.55 0.2 260); --cd-motion-pop-dur: 140ms; }", "filename": "candor-brand.css" }

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "required": [
      "css"
    ],
    "properties": {
      "css": {
        "type": "string",
        "maxLength": 262144,
        "description": "The CSS to check: the whole text of candor-brand.css (at most 256 KB)."
      },
      "filename": {
        "type": "string",
        "maxLength": 100,
        "description": "What to call it in findings (default candor-brand.css)."
      }
    }
  }

  arguments 18 lines copy
• item_changes unknown never probed

  What changed in one item between two released versions, from facts only, to plan an update and write its PR: props added, removed or retyped, exports and LocaleProvider string keys added or removed, and files touched, from each release's API record; then the CHANGELOG entries in the range that name the item or its exports. Plain words first, then the same as JSON. Records start at 2.7.0: for an earlier version it says "not recorded before 2.7.0" and what is known from the first recorded release on, never a guess. `from` is the version the project has (candor-lock.json records it), and defaults to the one the server URL passes (`?kit=`, written by `npx candor-ui mcp`); `to` defaults to the latest. Example arguments: { "item": "plan", "from": "2.7.0", "to": "2.8.0" }

  mcp-tool

  1234567891011121314151617181920

  {
    "type": "object",
    "required": [
      "item"
    ],
    "properties": {
      "to": {
        "type": "string",
        "description": "The version to compare with. Default: the latest."
      },
      "from": {
        "type": "string",
        "description": "The version installed, e.g. \"2.7.0\" (candor-lock.json records it). Default: the version the server's URL passes (`?kit=`), which `npx candor-ui mcp` writes from the lockfile."
      },
      "item": {
        "type": "string",
        "description": "The registry name, e.g. \"plan\" or \"approval-request\"."
      }
    }
  }

  arguments 20 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.