Intento Translation MCP Server

Created By
intentoa year ago
Intento Translate MCP server
Overview

what is Intento Translation MCP Server?

Intento Translation MCP Server is a server that provides translation capabilities using the Intento API, allowing users to translate text between various languages.

how to use Intento Translation MCP Server?

To use the server, install the required dependencies, set up your Intento API credentials, and start the server using Python. You can then use the provided translation tools to translate text.

key features of Intento Translation MCP Server?

  • Translates text between languages using the Intento API.
  • Supports automatic language detection.
  • Provides a resource for mapping language names to ISO codes.
  • Comprehensive error handling and logging.

use cases of Intento Translation MCP Server?

  1. Translating documents or text for multilingual applications.
  2. Integrating translation capabilities into other software via the MCP protocol.
  3. Providing real-time translation services in chat applications.

FAQ from Intento Translation MCP Server?

  • What languages does the server support?

The server supports a wide range of languages as defined by the Intento API.

  • How do I set up my API key?

You can set up your API key by creating a .env file in the project root or by specifying it in your MCP configuration file.

  • Is there error handling in the server?

Yes, the server includes comprehensive error handling and logs all operations.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
intento
Star
1
Language
Python
License
Apache-2.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
Crevio

2 days ago