Vale MCP Server
> [!IMPORTANT]
> I am now co-developing https://github.com/ChrisChinchilla/Vale-MCP together with @[ChrisW](https://github.com/ChrisChinchilla). Head over there for new releases!
## AI usage disclosure
I've created this project using Claude Code with the Claude 4.5 model.
## License
This project is licensed under the MIT License. Refer to the [LICENSE](LICENSE) file for details.
TDQS
Scored across 3 tools
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.
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.
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.
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.