Mcp Simplelocalize

Created By
GalvinGaoa year ago
A MCP (Model Context Protocol) server implementation for SimpleLocalize.
Overview

What is Mcp Simplelocalize?

Mcp Simplelocalize is a server implementation of the Model Context Protocol (MCP) designed for use with SimpleLocalize, a localization tool that helps developers manage translations in their projects.

How to use Mcp Simplelocalize?

To use Mcp Simplelocalize, follow these steps:

  1. Install the required tool 'uv'.
  2. Clone the repository from GitHub.
  3. Install the necessary dependencies.
  4. Configure your project settings in the '.cursor/mcp.json' file, including your SimpleLocalize API key.
  5. Define your localization requirements in the '.cursorrules' file.
  6. Start using the tool to localize components in your project.

Key features of Mcp Simplelocalize?

  • Easy integration with SimpleLocalize for managing translations.
  • Supports multiple language codes including en-US, ja-JP, ko-KR, and zh-Hant.
  • Customizable project localization requirements.
  • Open-source with contributions welcome.

Use cases of Mcp Simplelocalize?

  1. Localizing web applications to support multiple languages.
  2. Managing translation files efficiently in software development projects.
  3. Automating the localization process for components in a project.

FAQ from Mcp Simplelocalize?

  • Is Mcp Simplelocalize free to use?

Yes! Mcp Simplelocalize is open-source and free to use under the MIT License.

  • What programming language is Mcp Simplelocalize written in?

Mcp Simplelocalize is written in Python.

  • How can I contribute to the project?

Contributions are welcome! You can open an issue or submit a pull request on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
GalvinGao
Star
3
Language
Python
License
MIT 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