Candor UI docs

com.themethodic/candorVersion 6.1.0

Candor UI docs and component suggestions. Read-only, no key, never serves paid source.

Status

Responds211 msNov 14, 2026, 14:18 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:18 UTC
Latency: 211 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 21:12 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://candor.themethodic.com/mcpResponds211 msNov 14, 2026, 14:18 UTC

No sign-in

Claude Code

claude mcp add --transport http candor https://candor.themethodic.com/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: candor
Remote MCP server URL: https://candor.themethodic.com/mcp

Cursor

{
  "mcpServers": {
    "candor": {
      "url": "https://candor.themethodic.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"candor","type":"http","url":"https://candor.themethodic.com/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

13 tools

Tools of Candor UI docs
	Description		Read-only	Idempotent	Open world
`get_brief`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).	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).	No	Yes	Yes	No
`get_component_docs`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.	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.	No	Yes	Yes	No
`get_design`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).	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).	No	Yes	Yes	No
`get_pattern`Read a pattern as Markdown: a common problem in agent UIs (approvals, traces, cost guards, …) and the components that solve it.	Read a pattern as Markdown: a common problem in agent UIs (approvals, traces, cost guards, …) and the components that solve it.	No	Yes	Yes	No
`get_review_checklist`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.	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.	No	Yes	Yes	No
`get_screen`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.	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.	No	Yes	Yes	No
`get_started`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).	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).	No	Yes	Yes	No
`item_changes`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" }	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" }	No	Yes	Yes	No
`list_components`List every item by group (Chat, Agent work, App shell, …), or one group's items with descriptions.	List every item by group (Chat, Agent work, App shell, …), or one group's items with descriptions.	No	Yes	Yes	No
`list_screens`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.	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.	No	Yes	Yes	No
`search_docs`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.	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.	No	Yes	Yes	No
`suggest_components`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.	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.	No	Yes	Yes	No
`theme_check`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, for the base and then for each brand scope ([data-brand="<name>"], as the theme builder writes several brands in one file) as a theme of its own, labelled (Light in [data-brand="acme"]) and counted in the totals; 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; a --cd-show-* or --cd-draw-* value the Pro motion-drawings item has no drawing for, as motion-value, with the values it takes; 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 and, for a brand scope's, its brand, 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" }	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, for the base and then for each brand scope ([data-brand="<name>"], as the theme builder writes several brands in one file) as a theme of its own, labelled (Light in [data-brand="acme"]) and counted in the totals; 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; a --cd-show-* or --cd-draw-* value the Pro motion-drawings item has no drawing for, as motion-value, with the values it takes; 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 and, for a brand scope's, its brand, 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" }	No	Yes	Yes	No

Details

Registry status: Active
Published: Nov 14, 2026
Updated: Nov 14, 2026
Website: https://candor.themethodic.com/⁠ (opens in a new tab)
Repository: https://github.com/MethodicDev/candor⁠ (opens in a new tab)
Categories (suggested): Knowledge and notesSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing