Candor UI docs and component suggestions. Read-only, no key, never serves paid source.
Connect Remote server
claude mcp add --transport http candor https://candor.themethodic.com/mcp
{
"mcpServers": {
"candor": {
"url": "https://candor.themethodic.com/mcp"
}
}
}
{
"servers": {
"candor": {
"type": "http",
"url": "https://candor.themethodic.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://candor.themethodic.com/mcp
Tools 13 found in our last check
search_docsSearch 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.
get_component_docsRead 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.
suggest_componentsDescribe 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…
list_componentsList every item by group (Chat, Agent work, App shell, …), or one group's items with descriptions.
get_patternRead a pattern as Markdown: a common problem in agent UIs (approvals, traces, cost guards, …) and the components that solve it.
list_screensList 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.
get_screenRead 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.
get_startedHow 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…
get_briefOne 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 rule…
get_designThe 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 an…
get_review_checklistThe 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…
theme_checkCheck 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…
item_changesWhat 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…
Details
| Endpoint | https://candor.themethodic.com/mcp (Streamable HTTP) |
| First published | 13 Nov 2026 |
| Last updated | 13 Nov 2026 |
| Registry name | com.themethodic/candor |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
