Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
discoverA

Discover the complete i18n setup. Returns project config (locales, default locale, layers, fallback chain, glossary, translation style) plus per-layer directory listings with file counts and top-level key namespaces. Call this first — it warms the config cache that all other tools depend on.

list_namespacesA

List the translation key tree grouped by namespace prefix. Returns a hierarchical view of all keys with counts per namespace node. Use this to explore available keys without guessing path prefixes.

get_translationsA

Get translation values for given key paths from a specific locale and layer. Use "*" as locale to read from all locales.

write_translationsA

Write translation key-value pairs to a layer. Mode "upsert" adds new keys and updates existing ones (default, most common). Mode "add" only creates new keys, skipping existing ones. Mode "update" only modifies existing keys, skipping missing ones. Keys are inserted in alphabetical order. Use dryRun to preview without writing.

get_missing_translationsA

Find translation keys that exist in the reference locale but are missing in other locales. Scans a specific layer or all layers.

search_translationsA

Search translation files by key path or value. Simple case-insensitive substring match — not fuzzy or regex. Useful for finding existing translations before adding duplicates.

remove_translationsA

Remove one or more translation keys from ALL locale files in the specified layer. Use dryRun to preview changes before applying them.

rename_translation_keyA

Rename/move a translation key across ALL locale files in a layer. Preserves the value in every locale. Use dryRun to preview changes before applying them.

translate_missingA

Find keys missing in target locales and translate them. Uses the host LLM via MCP sampling if available, otherwise returns context for the agent to translate inline. Uses project config (glossary, translation prompt, locale notes, examples) if available. Translates all locales concurrently by default — pass all targetLocales at once.

translate_keyA

Add/update one source translation key and translate it into target locales. Unlike translate_missing, this can overwrite existing stale target translations.

find_orphan_keysA

Find translation keys that exist in locale JSON files but are not referenced in any Vue/TS source code. Scans a specific layer or all layers. Reports keys that can potentially be removed. Also detects dynamic key patterns and uncertain matches.

remove_orphan_keysA

Find orphan keys (not referenced in source code) and remove them from all locale files. Always does a dry run first.

scaffold_localeA

Create empty locale files for new languages. Copies the key structure from the default locale with all values set to empty strings. Supports both JSON (Nuxt) and PHP (Laravel) formats. Does NOT modify framework config — the agent must add the locale to the framework config before calling this tool.

Prompts

Interactive templates invoked by user choice

NameDescription
add-feature-translationsGuided workflow for adding i18n translations when building a new feature.
add-languageAdd a new language to the project: update framework config, scaffold empty locale files, then translate all keys.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fabkho/the-i18n-kit'

If you have feedback or need assistance with the MCP directory API, please join our Discord server