Lingvanex Translate

Created By
lingvanex-mt4 months ago
Overview

What is Lingvanex Translate?

Lingvanex Translate is a Model Context Protocol (MCP) server designed for text translation, allowing users to translate text between different languages using a simple API.

How to use Lingvanex Translate?

To use Lingvanex Translate, you need to set up a Lingvanex account, obtain an API key, and run the server either in stdio mode for integration with Claude Desktop or in HTTP mode for browser testing.

Key features of Lingvanex Translate?

  • Supports multiple transport modes (stdio and HTTP)
  • Easy integration with Claude Desktop
  • Provides a simple API for text translation

Use cases of Lingvanex Translate?

  1. Translating text for applications and websites.
  2. Integrating translation capabilities into chatbots.
  3. Assisting users in multilingual communication.

FAQ from Lingvanex Translate?

  • Do I need a payment card to sign up for a Lingvanex account?

No, you can sign up for a free trial without adding a payment card.

  • What programming languages can I use to interact with the API?

You can use any programming language that supports HTTP requests to interact with the API.

  • How do I test the server after setup?

You can test the server by sending a request to the local HTTP endpoint using curl.

Server Config

{
  "mcpServers": {
    "translate": {
      "command": "node",
      "args": [
        "C:\\Users\\path\\to\\project\\dist\\index.js"
      ]
    }
  }
}
Project Info
Created At
4 months ago
Updated At
4 months ago
Author Name
lingvanex-mt
Star
-
Language
-
License
-

Recommend Servers

View All
Crevio

a day 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)

19 hours ago