i18n Hardcoded String Detector Connector for AI agents.
3 live capabilities
Catch un-translated text in your frontend codebase.
Waiting for input…
Why people use i18n Hardcoded String Detector
Stop shipping hardcoded text with i18n Hardcoded String Detector
This Connector automates the audit, finding every violation in seconds. You get a clear list of exactly what needs fixing.
What Vinkius changes
You stop shipping broken, single-language UIs.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 6,100+ Connectors
- Real-world use case 01
Finding missed strings in a React PR
A developer submits a large PR with new components, and the agent uses analyze_codebase to ensure no English text slipped through.
- Real-world use case 02
Cleaning up old translation keys
After a major refactor, you use audit_strings to identify which keys in your JSON files are now orphans.
- Real-world use case 03
Validating new localization files
You just added a new language and need to ensure the syntax is perfect before deployment.
Complete set · 3capabilities
The complete i18n Hardcoded String Detector capability set.
These are the exact actions your AI can choose when you ask it to work with i18n Hardcoded String Detector.
01—03
3 capabilities in this set.
Part of 3 available through i18n Hardcoded String Detector.
- 01 Capability
Audit strings
Compares found strings against your translation dictionary. This identifies both hardcoded text and keys that are no longer needed.
- 02 Capability
Verify dictionary syntax
Checks your JSON or JS translation files for structural errors. It ensures your agent can actually read the dictionary without crashing.
- 03 Capability
Analyze codebase
Scans your project directory to find every piece of user-facing text. It uses AST parsing to be precise about what is actually a UI string.
Set up in minutes
One URL. Then ask i18n Hardcoded String Detector to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use i18n Hardcoded String Detector from the conversation.
Choose your client
Live previewAdvanced clients IDE · CLI
Claude · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_MnZ7GP6wyVNT1qGzNQAkSfdyJd8ZduAumjbqc3sn/mcp - Step 01
Open Connectors
In Claude Web or Claude Desktop, open Settings and choose Connectors.
- Step 02
Add the URL
Choose Add custom connector, name it i18n Hardcoded String Detector, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable i18n Hardcoded String Detector for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_MnZ7GP6wyVNT1qGzNQAkSfdyJd8ZduAumjbqc3sn/mcp - Step 01
Open MCP settings
On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
- Step 02
Add the URL
Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the i18n Hardcoded String Detector URL.
- Step 03
Save and start
Save the connection and enable i18n Hardcoded String Detector in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"i18n-hardcoded-string-detector": {
"url": "https://edge.vinkius.com/vk_preview_MnZ7GP6wyVNT1qGzNQAkSfdyJd8ZduAumjbqc3sn/mcp"
}
}
}- Step 01
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
- Step 02
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
- Step 03
Save the file
Cursor will automatically detect the new Connector
- Step 04
Start using i18n Hardcoded String Detector
Open Agent mode in chat and ask: "Using i18n Hardcoded String Detector, help me...". 3 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"i18n-hardcoded-string-detector": {
"url": "https://edge.vinkius.com/vk_preview_MnZ7GP6wyVNT1qGzNQAkSfdyJd8ZduAumjbqc3sn/mcp"
}
}
}- Step 01
Create MCP config
Create a .vscode/mcp.json file in your project root
- Step 02
Add the server config
Paste the JSON configuration above
- Step 03
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
- Step 04
Start using i18n Hardcoded String Detector
Ask Copilot: "Using i18n Hardcoded String Detector, help me...". 3 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"i18n-hardcoded-string-detector": {
"url": "https://edge.vinkius.com/vk_preview_MnZ7GP6wyVNT1qGzNQAkSfdyJd8ZduAumjbqc3sn/mcp"
}
}
}- Step 01
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
- Step 02
Add the server
Paste the JSON configuration above into mcp_config.json
- Step 03
Save and reload
Windsurf will detect the new server automatically
- Step 04
Start using i18n Hardcoded String Detector
Open Cascade and ask: "Using i18n Hardcoded String Detector, help me...". 3 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"i18n-hardcoded-string-detector": {
"url": "https://edge.vinkius.com/vk_preview_MnZ7GP6wyVNT1qGzNQAkSfdyJd8ZduAumjbqc3sn/mcp"
}
}
}- Step 01
Open Cline MCP Settings
Click the Connectors icon in the Cline sidebar panel
- Step 02
Add remote server
Click "Add Connector" and paste the configuration above
- Step 03
Enable the server
Toggle the server switch to ON
- Step 04
Start using i18n Hardcoded String Detector
Ask Cline: "Using i18n Hardcoded String Detector, help me...". 3 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add i18n-hardcoded-string-detector --transport http "https://edge.vinkius.com/vk_preview_MnZ7GP6wyVNT1qGzNQAkSfdyJd8ZduAumjbqc3sn/mcp"- Step 01
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
- Step 02
Add the Connector
Run the command above in your terminal
- Step 03
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
- Step 04
Start using i18n Hardcoded String Detector
Ask Claude: "Using i18n Hardcoded String Detector, show me...". 3 tools are ready
Where the request belongs
Work i18n Hardcoded String Detector can move forward.
Frontend engineers tired of manual audits, localization managers ensuring coverage, and QA engineers catching UI regressions.
Frontend Engineer
Checking React components for hardcoded labels during a pull request.
Localization Lead
Verifying that all new features have corresponding keys in the JSON translation files.
QA Automation Engineer
Running automated checks to ensure no English text leaked into localized test environments.
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse ConnectorsPhrase (Software Localization API)
Manage software localization projects, locales, and translation keys directly through the Phrase API.
Transifex
Localize your projects efficiently using AI Agents with the official Transifex integration.
Localazy (AI Translation & Localization API)
Manage software localization and translations via Localazy. list projects, import content, manage source keys, and handle glossary terms directly from your AI agent.
Crowdin
Equip your AI agent to manage localization projects, files, and translations directly via the Crowdin API.
Localization Readiness Checker
Identify linguistic, cultural, and structural risks in your source text to ensure high-quality localization.
Lokalise
Automate translation and localization workflows via Lokalise. manage projects, keys, and translations directly from any AI agent.
Bring your own AI
Change the model, client or framework. Keep i18n Hardcoded String Detector connected.
-
Claude -
ChatGPT -
Gemini -
Cursor -
VS Code -
Windsurf -
ZCode -
Cline -
Zed -
Continue -
Kiro -
Roo Code -
Zencoder -
Goose -
Void -
Augment Code -
Amp -
Qodo -
Tabnine -
Pieces -
Sourcegraph Cody -
JetBrains -
Warp -
Amazon Q -
Antigravity -
BoltAI -
Raycast -
Jan -
LM Studio -
AnythingLLM -
Open WebUI -
Msty -
Cherry Studio -
LibreChat -
TypingMind -
Chorus -
5ire -
n8n -
LangChain -
LlamaIndex -
CrewAI -
Vercel AI SDK
Before you connect
Questions about i18n Hardcoded String Detector.
The practical details behind the request, access and result.
How can I find missing translations with i18n Hardcoded String Detector?
You can run a scan on your codebase to identify any text that isn't linked to a translation key. This helps you catch English labels before they are deployed.
Does i18n Hardcoded String Detector work with React and JSX?
Yes, it specifically parses JSX and HTML nodes to find user-facing text. It is designed for modern frontend frameworks.
Can I use i18n Hardcoded String Detector to clean up my JSON files?
Absolutely. You can identify keys that are no longer used in your components so you can safely remove them from your translation dictionaries.
Will i18n Hardcoded String Detector catch aria-labels?
Yes, the capability scans attributes like aria-labels to ensure your accessibility text is also properly internationalized.
Is it possible to verify my translation file syntax with this Connector?
Yes, you can check your JSON or JS dictionary files for structural errors to prevent broken builds during deployment.
How does the capability identify strings without using regex?
The capability performs deterministic AST traversal to distinguish between actual UI text nodes and technical identifiers like CSS classes or console logs.
Can I use `audit_strings` with any translation format?
Yes, as long as you provide the extracted keys and values from your dictionary to the capability.
What does a 'hardcoded' violation mean?
A violation is flagged when a string literal found in your UI (via analyze_codebase) does not exist as a key or value in your translation dictionary.
One connection away
Give your agent a direct line to i18n Hardcoded String Detector.
Connect i18n Hardcoded String Detector once. Keep it beside 6,100+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available