Localization support for prompts/list and Japanese text encoding issue

[yotsuda]

Pre-submission Checklist

• I have verified that this discussion would not be more appropriate as an issue in a specific repository
• I have searched existing discussions to avoid duplicates

Discussion Topic

Is there a way to localize the prompts/list response? While the text field doesn't necessarily need to be localizable, I believe the name and description fields should support localization.

Currently, when implementing MCP servers that serve users in different languages, we're limited to providing prompts in a single language. Having localization support for at least the prompt names and descriptions would greatly improve the user experience for non-English speaking users.

Additionally, I've encountered an issue where Japanese text in the text field appears garbled in Claude Desktop. Is there a known workaround for this encoding issue?

Has anyone found workarounds for either of these issues, or are there plans to add official localization support and fix the text encoding problems in the MCP specification?

[yotsuda]

Update: Resolved

I've found a solution to the localization issue. It turns out that localization is indeed possible by creating custom attribute classes in the MCP SDK.

Technical Implementation:

• Created custom attributes (LocalizedNameAttribute, ResourceDescriptionAttribute, LocalizedParameterNameAttribute) that leverage .NET's ResourceManager
• Uses .resx resource files (e.g., PromptDescriptions.resx for default language, PromptDescriptions.ja-JP.resx for Japanese)
• Automatic language switching based on CultureInfo.CurrentUICulture
• Applies to MCP prompt names, descriptions, and parameter descriptions

For anyone facing similar localization needs, you can refer to my implementation here:
https://github.com/yotsuda/PowerShell.MCP/tree/main/PowerShell.MCP.Proxy/Attributes

Regarding the Japanese text encoding issue in the text field on Claude Desktop, this appears to be resolved with the custom attribute implementation as well.

Closing this discussion as the issue has been resolved.