Vale MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VALE_CONFIG_PATH | No | Explicit path to Vale configuration file |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.