Claude Multi-File Coherence Checker Connector for AI agents.

It acts as a validation layer that checks if changes to one file have broken the imports, function calls, or type definitions in other files. It catches the errors that happen when an AI agent updates a definition but misses its consumers.

Yes, it is specifically designed to handle the complexities of TypeScript, including type propagation and interface consistency across multiple files.

No. While linters catch syntax and style issues, this MCP focuses on the structural relationship between different files, catching errors that occur during multi-file refactors that a standard linter might miss.

You connect the MCP through Vinkius. Once connected, your agent in Cursor will have access to the validation capabilities to check your code's integrity automatically.

Yes, that is its primary purpose. It helps ensure that when you perform massive changes across a large codebase, the structural links between files remain intact.

It solves the problem of partial updates, where an AI agent modifies a function or type in one file but misses the corresponding updates in other files that use them.

By using validate_import_coherence, the capability maps exported symbols in changed files and scans the project for import statements that no longer point to valid exports.

Yes, the check_signature_consistency capability specifically checks if modified function or class signatures still match their call sites, including parameter counts and types.