🌐 i18n MCP Server

Created By
reinier-milloa year ago
MCP server for handling i18n JSON files
Overview

What is i18n MCP Server?

The i18n MCP Server is a powerful tool designed for managing internationalization (i18n) in projects by handling JSON-based language files. It allows users to generate translations directly from a base language file using advanced language models through a convenient server interface.

How to use i18n MCP Server?

To use the i18n MCP Server, clone the repository, install the dependencies, build the server, and configure it within the Cursor IDE. Once set up, you can interact with the server using the Cursor Agent to manage translation tasks.

Key features of i18n MCP Server?

  • Multi-language support for automatic translation generation from a single base file.
  • Utilizes models on Cursor for translation without additional costs.
  • Streamlined workflow to eliminate manual duplication of JSON files.
  • Developer-friendly design for easy integration into development pipelines.

Use cases of i18n MCP Server?

  1. Automating the translation of web applications into multiple languages.
  2. Maintaining consistency in language files across different projects.
  3. Reducing manual effort in managing i18n files during app scaling.

FAQ from i18n MCP Server?

  • Can the i18n MCP Server handle all languages?

Yes, it supports multiple languages as defined in the base language file.

  • Is there a cost associated with using the i18n MCP Server?

No, it is free to use and does not require additional translation service payments.

  • How does the server ensure translation accuracy?

The accuracy depends on the language model used and the clarity of the base language file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
reinier-millo
Star
0
Language
TypeScript
License
AGPL-3.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago