calor mcp

Start the Model Context Protocol server used by coding agents.

Bash

calor mcp --stdio --root /absolute/project/path

Options

Option	Description
`--stdio`	Use standard input/output; enabled by default
`--verbose`, `-v`	Write debug logs to stderr
`--root`	Confine project sessions and file writes to this directory

Pin --root in harnesses and CI. Without it, write confinement falls back to the server process's working directory, which depends on how the client starts the process.

The v0.12 Tool Surface

The server registers 18 tools. Several older one-purpose names were folded into action-based tools; clients should discover the live tool list rather than assuming names from pre-v0.12 documentation.

Tool	Purpose
`calor_compile`	Compile source to C# and return auto-fix suggestions without writing
`calor_check`	Diagnostics, lint, type checking, or snippet validation
`calor_verify`	Seven-status Z3 contract verification with counterexamples
`calor_analyze`	Bug/security analysis, migration assessment, or interop minimization
`calor_convert`	Convert C# to Calor with issues and validation diagnostics
`calor_batch`	Batch convert, analyze, or compile a project
`calor_help`	Syntax, support, diagnostic, and example lookup
`calor_navigate`	Definition, reference, symbol, type, and scope queries
`calor_structure`	Outline, call graph, and change-impact analysis
`calor_edit_preview`	Classify a proposed edit as safe, warning-bearing, or breaking
`calor_format`	Format source or check/assign declaration IDs
`calor_session_open`	Parse a project and return a session for cross-file checks
`calor_session_close`	Release an open project session
`calor_file_write`	Heal, check, and atomically apply a confined `.calr` write
`calor_refine`	Refinement obligations, bounds, guards, fixes, and type suggestions
`calor_fix`	Return non-destructive fixes for common compiler errors
`calor_migrate`	Run the project migration pipeline; this tool can write files
`calor_self_test`	Check the compiler against embedded golden files

Diagnostic-producing tools use the shared schema 2.0 envelope inside their result DTOs. In particular, verification uses proven, refuted, assumed, unknown, timeout, unsupported, and unavailable.

Project Configuration

calor init --ai codex, --ai claude, --ai gemini, and --ai github write the client-specific MCP configuration. A direct Codex configuration is:

toml

[mcp_servers.calor]
command = "calor"
args = ["mcp", "--stdio", "--root", "/absolute/project/path"]

Keep human-oriented logging on stderr so the protocol stream stays clean. For write operations, prefer a project session plus calor_file_write; it checks cross-file references and applies the file atomically only after the requested checks pass.