Lingvanex Text Translator

Created By
lingvanex-mt8 months ago
Overview

what is Lingvanex Text Translator?

Lingvanex Text Translator is a Model Context Protocol (MCP) server that provides multilingual text translation using the Lingvanex API, allowing translation between more than 100 languages.

how to use Lingvanex Text Translator?

To use the Translator, create a Lingvanex account and obtain an API key. Install the necessary dependencies, build the project, and start the server in either stdio mode for Claude Desktop integration or HTTP mode for API access.

key features of Lingvanex Text Translator?

  • Multilingual text translation powered by Lingvanex API
  • Supports stdio for Claude Desktop and HTTP for API access
  • Easy integration with Claude Desktop
  • Lightweight translation API for external tools
  • Simple tool interface for text translation

use cases of Lingvanex Text Translator?

  1. Translating user prompts or documents in Claude Desktop
  2. Using the HTTP server as a local API for custom applications
  3. Connecting third-party tools to translation via HTTP endpoints
  4. Building multilingual assistants with MCP-compatible clients
  5. Learning and experimenting with MCP integration

FAQ from Lingvanex Text Translator?

  • Can it work without a Lingvanex API key?

No, a Lingvanex API key is required.

  • Is it free to use?

Yes, it is open-source and offers a free trial API key.

  • What transports are supported?

stdio for Claude Desktop and HTTP for API access.

  • What are the system requirements?

Node.js >= 18 and a Lingvanex API key are required.

Server Config

{
  "command": "node",
  "args": [
    "./dist/index.js"
  ],
  "env": {
    "TRANSPORT": "stdio",
    "LINGVANEX_API_KEY": "your_api_key_here"
  }
}
Project Info
Created At
8 months ago
Updated At
8 months ago
Author Name
lingvanex-mt
Star
-
Language
-
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