Hosting

Remote, hosted

Transport

Streamable HTTP

Endpoint

https://mcp-v2.laratranslate.com/v1

Authentication

OAuth 2.0 browser login is recommended. The official guide also documents Access Key ID and Secret headers as an alternative; store these in the client's secret manager, not in chat.

Requirements

• A Lara Translate account and subscription; exact plan entitlements are not specified in the setup guide.
• An MCP client that supports remote HTTP servers and OAuth, or a client-specific documented configuration.
• Node.js v18+ is required only for the documented Claude Desktop mcp-remote bridge used with Access Key authentication.

Setup steps

1. Add https://mcp-v2.laratranslate.com/v1 to the chosen MCP client using its documented remote-server configuration.
2. Complete Lara Translate browser login when the client requests authentication.
3. Alternatively, create Access Key ID and Secret in the Lara account and configure them as x-lara-access-key-id and x-lara-access-key-secret headers using secure local storage.
4. Reload or restart the client if its setup guide requires it.
5. Verify with a harmless request such as translating ?Hello world? to Spanish.

Official hosted tool reference lists 22 tools, matching the stored names across translation, detection, translation memory and glossary features.

• translate

  Translate text using context, instructions, translation memories, glossaries, and styles.

  01
• detect_language

  Detect the language of one or more text inputs.

  02
• list_languages

  List supported language codes.

  03
• list_memories

  List translation memories in the account.

  04
• create_memory

  Create a translation memory.

  05
• update_memory

  Update a translation memory name.

  06
• delete_memory

  Delete a translation memory.

  07
• add_translation

  Add a source/target translation unit to a memory.

  08
• delete_translation

  Delete a translation unit.

  09
• import_tmx

  Import a TMX file into a memory.

  10
• check_import_status

  Check a TMX import job.

  11
• list_glossaries

  List account glossaries.

  12
• get_glossary

  Get glossary details.

  13
• create_glossary

  Create a glossary.

  14
• update_glossary

  Update a glossary name.

  15
• delete_glossary

  Delete a glossary.

  16
• add_glossary_entry

  Add or replace a glossary term entry.

  17
• delete_glossary_entry

  Delete a glossary term entry.

  18
• import_glossary_csv

  Import glossary entries from CSV.

  19
• check_glossary_import_status

  Check a glossary CSV import job.

  20
• export_glossary

  Export a glossary as CSV.

  21
• get_glossary_counts

  Get the number of entries in a glossary.

  22

• Memory and glossary tools can create, change, or delete account data; confirm before invoking destructive operations.
• Access Key credentials are secrets and must be stored locally, not shared in chat.
• The linked setup guide lists Claude Desktop, Cursor, Claude Code, VS Code with GitHub Copilot, Windsurf, Cline, and Continue; this does not establish compatibility with every MCP client.

• official tool reference

  Lara’s hosted tool reference enumerates 22 tools across translation, language detection, translation memories and glossaries, matching stored names. OAuth 2.0 or access-key auth.

• official documentation or source

  Lara’s hosted tool reference enumerates 22 tools across translation, language detection, translation memories and glossaries, matching stored names. OAuth 2.0 or access-key auth.

Documentation checked 2026-10-28T13:00:03.000Z. Connection has not been runtime tested.