project-conventions

To enforce consistent error handling across CLI, MCP, and core commands, you should propagate exceptions in core commands rather than swallowing them. This ensures a uniform failure envelope across all execution surfaces.

The best way to prevent COM object leaks during Excel MCP development is to release all dynamic COM objects within finally blocks. This cleanup discipline ensures robust memory management across core command execution.

Maintaining cross-surface parity between MCP Server and CLI tooling requires codifying shared development conventions. This ensures both surfaces share a coherent contract and behave consistently during command execution.

ExcelMCP development drifts across surfaces because independent implementation of MCP Server, CLI, and core commands lacks unified conventions. Applying standardized checks and examples prevents this drift and restores reliability.

Yes, you need to apply these conventions when adding new CLI surface or MCP tools. Adopting these patterns during development ensures immediate parity, consistent error handling, and long-term maintainability.

Relying on ad-hoc patterns for ExcelMCP core commands limits cross-surface parity and risks COM interop leaks. Without codified conventions, error handling drifts and failure envelopes become inconsistent across MCP and CLI.