Docs/Candor Deploy
Deploy from Claude: connect the Candor MCP
Connect Claude to Candor Deploy so you can say 'deploy this to Candor' and it happens — set up the MCP server in Claude Code, Claude Desktop, and the web apps.
Candor Deploy runs an MCP server, so you can tell Claude to deploy an app and it does — detects the stack, provisions any databases, and hands back the live URL. This page connects Claude to your Candor account.
You’ll need a Candor API token. Open your client area, go to Deployments, and in the sidebar choose API tokens → Create token. Copy it — it’s shown once.
Claude Code
One command. Paste your token in place of YOUR_TOKEN:
claude mcp add --transport http candor https://api.candorhost.app/mcp --header "Authorization: Bearer YOUR_TOKEN"
That’s it. Ask Claude to deploy this repo to Candor and it will. To share the
connection with a repo instead, commit a .mcp.json at the project root:
{
"mcpServers": {
"candor": {
"type": "http",
"url": "https://api.candorhost.app/mcp",
"headers": { "Authorization": "Bearer ${CANDOR_TOKEN}" }
}
}
}
The ${CANDOR_TOKEN} reference is filled from your environment, so the token
itself never lands in the committed file — set CANDOR_TOKEN in your shell.
Claude Desktop
Claude Desktop reads the same shape from its config file
(claude_desktop_config.json, reachable from Settings → Developer → Edit
Config). Add:
{
"mcpServers": {
"candor": {
"type": "http",
"url": "https://api.candorhost.app/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}
Restart Claude Desktop and the Candor tools appear.
claude.ai and ChatGPT
The web apps add remote tools through their custom connector flows, which
require a sign-in (OAuth) rather than a pasted token. We’re building that — when
it ships, connecting will be: add the connector, point it at
https://api.candorhost.app/mcp, and sign in to Candor. No token to copy.
Until then, use Claude Code or Claude Desktop above — both take your token directly and work today.
What you can ask
Once connected, Claude has these tools:
- Deploy a repo — “deploy github.com/me/myapp to Candor.” Candor detects the stack, provisions databases it finds, and deploys. Push your latest commit first; Candor builds from your git remote.
- Check a deploy — “is my Candor deploy live yet?” — the phase, and the build logs if it failed.
- List what you’ve deployed — your projects, services, and their URLs.
If Candor can’t work out how to start a service, Claude will ask you for the start command rather than deploy something that won’t come up.
Security
Your token acts as your Candor account from wherever you paste it. It lives only where you put it — your machine’s Claude config — never on our servers in a form we can read; we store a hash. If a machine is lost, revoke that token in the portal (API tokens → Revoke) and it stops working immediately.
Something here wrong, unclear, or missing? Tell us — docs get fixed like bugs.