i18n Hardcoded String Detector

i18n Hardcoded String Detector MCP Connector for Claude

A+

An AST-powered auditing tool that identifies un-internationalized text literals in source code by cross-referencing them against translation dictionary keys.

3 tools Official Updated Oct 1, 2026 Official Vinkius Partner

The i18n Hardcoded String Detector uses advanced Abstract Syntax Tree (AST) parsing to find user-facing text that hasn't been internationalized. It scans your codebase for strings in JSX/HTML nodes, aria-label attributes, and UI labels, then compares them against your translation dictionary. Use analyze_codebase to extract candidate strings, verify_dictionary_syntax to check your JSON/JS files, and audit_strings to generate a report of hardcoded violations and orphaned keys.

i18nastauditcodebaseautomation

3 tools expose this connector's capabilities to your AI agent.

audit_strings

Compare discovered candidate strings against the translation dictionary

verify_dictionary_syntax

Ensure the translation dictionary is structurally sound

analyze_codebase

Identify all candidate user-facing string literals within a given directory

See how to talk to your AI agent using i18n Hardcoded String Detector.

Scan my React project for hardcoded strings.

I will use `analyze_codebase` on the specified path to identify all candidate UI strings using AST parsing.

Check if my en.json file is valid.

I will run `verify_dictionary_syntax` on the provided path to ensure the JSON structure is correct and readable.

Compare these strings against my translation keys.

I will use `audit_strings` with the provided candidate strings, dictionary keys, and values to generate a report of hardcoded text and orphaned keys.

The tool performs deterministic AST traversal to distinguish between actual UI text nodes and technical identifiers like CSS classes or console logs.

Related Connectors