smalltalk-validator-mcp-server
smalltalk-validator-mcp-server
A simple MCP server for validating and linting Tonel formatted Smalltalk source code using tree-sitter-tonel-smalltalk.
The purpose is that we would like to validate and lint AI-generated tonel files and Smalltalk method definitions before loading them into a real Smalltalk environment.
Tools
Validation Tools
validate_tonel_smalltalk_from_file(file_path, options)
Validate Tonel formatted Smalltalk source code from a file
validate_tonel_smalltalk(file_content, options)
Validate Tonel formatted Smalltalk source code from content string
validate_smalltalk_method_body(method_body_content)
Validate a Smalltalk method body for syntax correctness
Validation Options
without-method-body: true
if true, it only validates tonel structure only (mainly for testing)Linting Tools
lint_tonel_smalltalk_from_file(file_path)
Lint Tonel formatted Smalltalk source code from a file
lint_tonel_smalltalk(file_content)
Lint Tonel formatted Smalltalk source code from content string
See docs/lint-checks.md for the full list of checks.
Related MCP server: pharo-smalltalk-interop-mcp-server
Installation
Quick install (uvx)
Run directly without cloning:
uvx --from git+https://github.com/mumez/smalltalk-validator-mcp-server.git@main smalltalk-validator-mcp-serverDevelopment setup (git clone)
git clone https://github.com/mumez/smalltalk-validator-mcp-server.git
cd smalltalk-validator-mcp-server
uv syncUsage
Running the MCP Server
Using uvx (recommended for quick run):
uvx --from git+https://github.com/mumez/smalltalk-validator-mcp-server.git@main smalltalk-validator-mcp-serverFrom a cloned repo:
uv run smalltalk-validator-mcp-serverConfiguration Examples
Cursor Configuration
Add to your .cursor/settings.json:
{
"mcpServers": {
"smalltalk-validator": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/mumez/smalltalk-validator-mcp-server.git@main",
"smalltalk-validator-mcp-server"
]
}
}
}If you prefer using a local clone, use this instead:
{
"mcpServers": {
"smalltalk-validator": {
"command": "uv",
"args": [
"--directory",
"/path/to/smalltalk-validator-mcp-server",
"run",
"smalltalk-validator-mcp-server"
]
}
}
}Claude Code Configuration
Add to your Claude Code settings:
claude mcp add smalltalk-validator -- uvx --from git+https://github.com/mumez/smalltalk-validator-mcp-server.git@main smalltalk-validator-mcp-serverUsing a local clone instead:
claude mcp add smalltalk-validator -- uv --directory /path/to/smalltalk-validator-mcp-server run smalltalk-validator-mcp-serverTool Usage Examples
Validate Tonel file from filesystem
# Validate a complete Tonel file with method bodies
validate_tonel_smalltalk_from_file("/path/to/MyClass.st")
# Validate only Tonel structure (without method body validation)
validate_tonel_smalltalk_from_file("/path/to/MyClass.st", {"without-method-body": true})Validate Tonel content directly
tonel_content = """
Class {
#name : #MyClass,
#superclass : #Object,
#category : #'My-Package'
}
{ #category : #accessing }
MyClass >> getValue [
^ 42
]
"""
validate_tonel_smalltalk(tonel_content)Validate Smalltalk method body
method_body = "^ self name asUppercase"
validate_smalltalk_method_body(method_body)Lint Tonel file from filesystem
# Lint a Tonel file for best practices and style issues
result = lint_tonel_smalltalk_from_file("/path/to/MyClass.st")
# Example result:
# {
# "success": true,
# "file_path": "/path/to/MyClass.st",
# "issue_list": [
# {
# "severity": "warning",
# "message": "Method 'longMethod' long: 18 lines (recommended: 15)",
# "class_name": "MyClass",
# "selector": "longMethod",
# "is_class_method": false,
# "reference_url": "https://github.com/mumez/smalltalk-validator-mcp-server/blob/main/docs/lint-checks.md#method-too-long"
# }
# ],
# "issues_count": 1,
# "warnings_count": 0,
# "errors_count": 0
# }Lint Tonel content directly
tonel_content = """
Class {
#name : #MyClass,
#superclass : #Object,
#instVars : [
'name',
'age'
],
#category : #'My-Package'
}
{ #category : #accessing }
MyClass >> getName [
^ name
]
"""
result = lint_tonel_smalltalk(tonel_content)Development
# Install dependencies
uv sync
# Run tests
uv run pytest
# Lint and format
uv run ruff check
uv run ruff format
# Install pre-commit hooks
uv run pre-commit installAvailable Tools
5 toolslint_tonel_smalltalkLint Tonel Smalltalk ContentARead-onlyIdempotent
Lint Tonel formatted Smalltalk source code from content string.
Inputs: file_content (required). Returns: object
lint_tonel_smalltalk_from_fileLint Tonel Smalltalk FileARead-onlyIdempotent
Lint Tonel formatted Smalltalk source code from a file.
Inputs: file_path (required). Returns: object
validate_smalltalk_method_bodyValidate Smalltalk Method BodyARead-onlyIdempotent
Validate a Smalltalk method body for syntax correctness.
Inputs: method_body_content (required). Returns: object
validate_tonel_smalltalkValidate Tonel Smalltalk ContentARead-onlyIdempotent
Validate Tonel formatted Smalltalk source code from content string.
Inputs: file_content (required), options. Returns: object
validate_tonel_smalltalk_from_fileValidate Tonel Smalltalk FileARead-onlyIdempotent
Validate Tonel formatted Smalltalk source code from a file.
Inputs: file_path (required), options. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
The content/file distinction is clear, and validate_smalltalk_method_body is genuinely distinct, but lint vs validate pairs are highly similar in purpose and may cause an agent to select the wrong one without deeper semantics. Descriptions help only slightly because they don't define the exact boundary between linting and validating.
All tool names follow a consistent snake_case verb_noun pattern with an optional _from_file suffix. The naming is predictable across content-string and file-based variants, and validate_smalltalk_method_body fits the same style despite targeting a different input type.
Five tools is a well-scoped number for a focused Smalltalk source validator, covering both linting and validating across content strings and files, plus method body validation. No tool feels unnecessary, and the set is compact rather than bloated.
The core validation and linting workflows are covered for Tonel source code from both content strings and files, along with direct method-body validation. Minor gaps exist in the absence of batch processing, formatting, or a way to validate method bodies from files, but these are workable rather than blocking.
Maintenance
Related MCP Connectors
Lean 4 MCP server: compile, prove theorems, and formalize math with Mathlib.
The official Svelte MCP server providing docs and autofixing tools for Svelte development
MCP server for StyleKit styles, tokens, recipes, lint and repair over stdio or HTTP.
MCP Server for Slima - AI Writing IDE for Novel Authors with AI Beta Reader.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceStandalone MCP server for code structure analysis using tree-sitter. Directory trees, symbol definitions, and call graphs without reading raw source files. Supports Rust, Python, Go, Java, TypeScript, Fortran, JavaScript, C/C++, and C#. Benchmarked up to 68% fewer tokens vs native tools.7Apache 2.0
- AlicenseAqualityFmaintenanceMCP server to communicate local Pharo Smalltalk image2212MIT
- FlicenseAqualityDmaintenanceAn MCP server and CLI that uses Tree-sitter to parse and analyze code.1320-
- AlicenseNot gradedqualityBmaintenanceOffline static correctness MCP server for Godot 4.x GDScript projects that lints code, looks up API symbols, and validates scenes/resources, all without a running editor.240 npmCreative Commons Attribution Non Commercial No Derivatives 4.0 International