SpellChecker MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPELLCHECKER_CONFIG | No | Path to a spellchecker.config.json configuration file for setting languages and advanced scan options like fileTypes and ignorePaths. | |
| SPELLCHECKER_LANGUAGES | No | Comma-separated list of language codes to enable (e.g., 'en-US,es,fr'). Supported languages include en-US, en-GB, es, fr, de, pt, pt-BR, it, nl, pl, ru, uk, sv, da, nb. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_spellingC | Check spelling in the provided text and return misspellings with suggestions |
| add_to_dictionaryC | Add a word to the personal dictionary |
| is_correctA | Check if a single word is spelled correctly |
| get_suggestionsC | Get spelling suggestions for a word |
| list_languagesB | List all available languages for spell checking |
| check_fileC | Check spelling in a file with syntax-aware parsing |
| check_folderC | Check spelling in all files in a folder |
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 7 tools
Each tool has a clearly distinct purpose with no overlap: dictionary management (add_to_dictionary), file/folder checking (check_file, check_folder), text checking (check_spelling), word-level operations (get_suggestions, is_correct), and configuration (list_languages). The descriptions make it easy to differentiate between checking text vs. files vs. folders vs. single words.
All tools follow a consistent verb_noun naming pattern (e.g., add_to_dictionary, check_spelling, get_suggestions, list_languages). The verbs are clear and descriptive (add, check, get, is, list), and the snake_case style is applied uniformly throughout the set without any deviations.
With 7 tools, this server is well-scoped for a spell-checking domain. Each tool earns its place by covering distinct aspects: dictionary management, text/file checking, suggestions, correctness verification, and language support. The count is neither too thin nor bloated, fitting typical use cases effectively.
The tool set provides comprehensive coverage for core spell-checking workflows, including checking text/files/folders, getting suggestions, verifying correctness, managing dictionaries, and listing languages. A minor gap is the lack of tools for removing words from the dictionary or managing language settings, but agents can work around this with the existing tools.