Categories › Software Development › Library & API documentation lookup
Candor UI docs and component suggestions. Read-only, no key, never serves paid source.
Remote server: your requests and data go to candor.themethodic.com. Claude Code: claude mcp add --transport http candor-ui-docs https://candor.themethodic.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
search_docs — Search Candor UI's components, hooks, blocks and patterns by what they do ("approve a tool call", "cost estimate", "session list"). Returns 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, functisuggest_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 comlist_components — List every item by group (Chat, Agent work, App shell, …), or one group's items with descriptions.get_pattern — Read a pattern as Markdown: a common problem in agent UIs (approvals, traces, cost guards, …) and the components that solve it.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 foget_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), aget_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 `proget_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 copiget_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 tget_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 tetheme_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 eveitem_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 retypedNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.