smalltalk-validator

This MCP server provides validation and linting capabilities for Tonel formatted Smalltalk source via a smalltalk-validator toolset. It exposes validation functions such as validate_tonel_smalltalk_from_file, validate_tonel_smalltalk, and validate_smalltalk_method_body, along with linting utilities like lint_tonel_smalltalk_from_file and lint_tonel_smalltalk. The server is designed to help verify syntax and style before loading code into a Smalltalk environment, making it useful for AI-generated Tonel files and method bodies. To use it, run the MCP server through your preferred runner and connect with your editor or submission tooling; the server’s capabilities are exposed through the configured MCP interface so you can validate or lint by feeding file contents or strings according to the documented functions.

Tooling available:

• Validation: validate_tonel_smalltalk_from_file, validate_tonel_smalltalk, validate_smalltalk_method_body (with options like without-method-body to skip method-body validation).
• Linting: lint_tonel_smalltalk_from_file and lint_tonel_smalltalk for checks such as class naming, excessive instance variables, method length, and direct IV access.
• Configuration options allow you to tailor validation strictness (e.g., without-method-body).

Usage patterns typically involve passing either file paths or direct Tonel/Smalltalk content to the respective function calls, and optionally inspecting the returned results or issue lists to surface warnings or errors to developers or editors.

Prerequisites:

• Node.js/npm or a runtime capable of running UV-based processes (as provided by uvx).
• Internet access to fetch the MCP server from GitHub.

Step-by-step installation:

1. Quick start (uvx): uvx --from git+https://github.com/mumez/smalltalk-validator-mcp-server.git@main smalltalk-validator-mcp-server

2. Verify installation by starting the server via your preferred method (see usage docs in the repository) and confirming the smalltalk-validator MCP server is listed.

3. If you are integrating with an editor or IDE, configure your editor’s MCP settings to reference the smalltalk-validator MCP server using the provided command and arguments (as shown in the mcp_config example).

4. Optional: clone locally and run in development mode: git clone https://github.com/mumez/smalltalk-validator-mcp-server.git cd smalltalk-validator-mcp-server uvx --from git+https://github.com/mumez/smalltalk-validator-mcp-server.git@main smalltalk-validator-mcp-server

Notes:

• Ensure network access for uvx to fetch the repository.
• If you prefer local execution, point to a local clone as described in the repository README.

Tips and common issues:

• The server relies on Tonel parsing tooling; ensure that any dependencies required by the underlying Tonel parser are available in your runtime environment.
• When using without-method-body validation, the process is faster but does not verify method bodies; enable this if you need full syntax checks.
• If you encounter connectivity issues, verify that the git URL and branch (main) are accessible from your environment.
• For editors, ensure MCP integration points (like Cursor or Claude Code configurations) reference the correct command, directory, and server name as shown in the README examples.
• Use the linting options to enforce style guidelines such as class naming conventions and method length, which helps keep AI-generated code clean before integrating into a real Smalltalk environment.