Skip to main content
Glama
IMPORTANT

I am now co-developinghttps://github.com/ChrisChinchilla/Vale-MCP together with @ChrisW. Head over there for new releases!

AI usage disclosure

I've created this project using Claude Code with the Claude 4.5 model.

Related MCP server: MCP Code Checker

License

This project is licensed under the MIT License. Refer to the LICENSE file for details.

Available Tools

3 tools
check_fileA

Lint a file at a specific path against Vale style rules. Returns issues found with their locations and severity. If Vale is not installed, returns error with installation guidance.

Inputs: path (required).

vale_statusA

Check if Vale (vale.sh) is installed and accessible. Use this first if other Vale tools fail. Returns installation status, version if available, and installation instructions for the current platform.

Inputs: no named parameters.

vale_syncA

Download Vale styles and packages by running 'vale sync'. Use this when you see errors about missing styles directories (E100 errors like 'The path does not exist'). This command reads the .vale.ini configuration and downloads the required style packages.

Inputs: config_path.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: check_file performs linting, vale_status checks installation status, and vale_sync downloads styles. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the task at hand.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case: check_file, vale_status, and vale_sync. The naming is predictable and readable, with no deviations in style or convention.

    Tool Count5/5

    With 3 tools, the server is well-scoped for its purpose of Vale integration. Each tool earns its place by covering essential functions: installation check, style management, and linting, avoiding unnecessary complexity or redundancy.

    Completeness5/5

    The tool surface provides complete coverage for the Vale domain: vale_status handles setup verification, vale_sync manages style dependencies, and check_file performs the core linting operation. There are no obvious gaps, ensuring agents can handle the full workflow from installation to linting.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers