TranslationX MCP

Created By
dipa year ago
Overview

What is TranslationX MCP?

TranslationX MCP is a server application designed to facilitate translation tasks using a Python-based environment.

How to use TranslationX MCP?

To use TranslationX MCP, set up a Python virtual environment using uv, install the necessary dependencies, and run the MCP server with your translation tasks.

Key features of TranslationX MCP?

  • Easy setup with Python virtual environments
  • Integration with Cursor for seamless translation management
  • Support for custom translation tasks through a command-line interface

Use cases of TranslationX MCP?

  1. Automating translation processes for software development projects.
  2. Managing translation tasks in collaborative environments.
  3. Integrating translation capabilities into existing applications.

FAQ from TranslationX MCP?

  • What is required to run TranslationX MCP?

You need Python 3.13 or higher and the uv package to set up the environment.

  • Can I use TranslationX MCP for any type of translation?

Yes, it can be configured for various translation tasks as per your requirements.

  • Is there a graphical interface for TranslationX MCP?

Currently, it operates primarily through command-line interface, but it can be integrated with other tools for enhanced functionality.

Server Config

{
  "mcpServers": {
    "translationx": {
      "command": "uv",
      "args": [
        "run",
        "--with",
        "mcp[cli]",
        "mcp",
        "run",
        "{YOUR_PATH}/src/main.py"
      ],
      "env": {
        "token": "<YOUR_TRANSLATIONX_TOKEN>"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dip
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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