midnight-mcp:mcp-format

You can format Compact source code by passing it as a string to the midnight-format-contract MCP formatter, which returns consistently formatted output without writing to disk.

Yes, you can pass a versions parameter to run multi-version checks, comparing the formatted Compact code outputs across different compiler versions to detect version-specific style differences.

The formatter handles parse failures, rate limits, timeouts, and service errors safely by presenting the original unformatted code with clear diagnostics instead of risking file modification.

No, the formatter operates in-memory by accepting code strings and returning formatted output, preventing style inconsistencies and avoiding accidental in-place modifications caused by local formatters.

Use this formatter whenever Compact code will be presented or stored, including generated examples, file previews, documentation snippets, and multi-version consistency checks before presentation.

The service returns the formatted output, a changed flag indicating if modifications were made, diffs when available, and structured parse or service errors for diagnostics.