Skip to main content The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench Explore Tool Discovery
Live 47 Actions

Lara Translate MCP Server
for AI Agents

Connect your AI agent to StackOne's Lara Translate MCP server and give it 47 MCP tools out of the box. Auth, tool execution, and security all managed.

Lara Translate logo
Lara Translate MCP Server
Built by StackOne StackOne
DrataGPLocalyzeFlipMindtoolsScreenloop

Coverage

47 Agent Actions

Create, read, update, and delete across Lara Translate — and extend your agent's capabilities with custom actions.

Authentication

Agent Tool Authentication

Per-user OAuth in one call. Your Lara Translate MCP server gets session-scoped tokens with zero credentials stored on your infra.

Agent Auth →

Security

Agent Protection

Every Lara Translate tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.

Prompt Injection Defense →

Performance

Max Agent Context. Min Cost.

Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Lara Translate call.

Tools Discovery →

What is the Lara Translate MCP Server?

A Lara Translate MCP server lets AI agents read and write Lara Translate data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's Lara Translate MCP server ships with 47 pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, observability, and agent execution runtime. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.

All Lara Translate MCP Tools

Every action from Lara Translate's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.

Glossarys

  • Create Glossary

    Create a new empty glossary for the account.

  • Get Glossary

    Fetch a single glossary by ID.

  • Update Glossary

    Rename an existing glossary.

  • Delete Glossary

    Delete a glossary and all its entries.

Translation Memorys

  • Create Translation Memory

    Create a new translation memory for the account.

  • Get Translation Memory

    Fetch a single translation memory by ID.

  • Update Translation Memory

    Rename an existing translation memory.

  • Delete Translation Memory

    Delete a translation memory and all its contents.

Style Guides

  • Create Style Guide

    Create a new Lara Prosa style guide with a name and free-text guidance.

  • List Style Guides

    List all Lara Prosa style guides owned by the calling account.

  • Get Style Guide

    Fetch a single style guide by ID.

  • Update Style Guide

    Update a style guide's name, content, or both.

  • Delete Style Guide

    Delete a style guide.

Other (34)

  • Create Audio Translation Job

    Start an asynchronous audio-to-audio translation job from a previously uploaded S3 key.

  • Create Audio Transcript Translation Job

    Start an asynchronous speech-to-text plus translation job producing a translated transcript.

  • Create Document Translation Job

    Start an asynchronous document translation job from a previously uploaded S3 key.

  • Import CSV Into Glossary

    Import a CSV file into an existing glossary.

  • Add Or Replace Glossary Entry

    Add or replace a glossary entry with a set of language and value terms.

  • Import TMX Into Translation Memory

    Import a TMX file into an existing translation memory.

  • Add Translation Unit To Memory

    Add a translation unit (source sentence plus approved translation) to a translation memory.

  • Add Translation Unit To Multiple Memories

    Add the same translation unit to multiple translation memories in a single call.

  • Get Audio Upload URL

    Get a pre-signed S3 upload URL for an audio file to be translated.

  • Get Audio Job Status

    Get the current status of an audio translation job.

  • Get Audio Download URL

    Get a pre-signed S3 download URL for a completed audio-to-audio translation.

  • Get Translated Audio Transcript

    Fetch the translated transcript produced by an audio transcript translation job.

  • Get Document Upload URL

    Get a pre-signed S3 upload URL for a document to be translated.

  • Get Document Status

    Get the current status of a document translation job.

  • Get Document Download URL

    Get a pre-signed S3 download URL for a completed document translation.

  • List Glossaries

    List all glossaries owned by the calling account.

  • Get Glossary Import Job Status

    Get the progress of a glossary import job.

  • Export Glossary (Sync)

    Export a glossary synchronously as CSV.

  • Export Glossary (Async)

    Start an asynchronous export of a glossary to a downloadable archive.

  • Get Glossary Term Counts

    Get the number of unidirectional (per source language) and multidirectional entries in a glossary.

  • List Translation Memories

    List all translation memories owned by the calling account.

  • Get Memory Import Job Status

    Get the progress of a memory import job.

  • Export Translation Memory (Async)

    Start an asynchronous export of a translation memory to a downloadable archive.

  • List Supported Languages

    List all languages supported by the Lara translation engine.

  • Delete Glossary Entry

    Delete a glossary entry by term (unidirectional) or GUID (multidirectional).

  • Delete Translation Unit From Memory

    Delete a translation unit from a translation memory using its tuid or sentence and translation pair.

  • Delete Translation Unit From Multiple Memories

    Delete the same translation unit from multiple translation memories in a single call.

  • Detect Language

    Detect the language of a text string or an array of strings.

  • Detect Profanities

    Scan text for profanities in a specified language.

  • Estimate Translation Quality

    Score the quality of a candidate translation between two languages.

  • Translate Image

    Translate the text in an image and re-render the translated image using overlay, inpainting, or generative rendering.

  • Translate Image Text

    OCR and translate the text in an image and return the extracted paragraphs plus their translations without re-rendering the image.

  • Connect Existing Translation Memories

    Attach existing MyMemory memories to the calling Lara account by external MyMemory ID.

  • Translate Text

    Translate a text string or array of strings between two languages.

Set Up Your Lara Translate MCP Server in Minutes

One endpoint. Any framework. Your agent is talking to Lara Translate in under 10 lines of code.

Agent Frameworks

Claude Desktop
{
  "mcpServers": {
    "stackone": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.stackone.com/mcp?x-account-id=<account_id>",
        "--header",
        "Authorization: Basic <YOUR_BASE64_TOKEN>"
      ]
    }
  }
}

Lara Translate MCP Server FAQ

Does StackOne have a Lara Translate MCP server?
Yes. StackOne offers a hosted Lara Translate MCP server with 47 pre-built actions, and every action is tested and QA'd by StackOne. Connect it to Claude, Cursor, and any other MCP client, or to any agent framework through the AI Action SDK. It ships with managed agent authentication, prompt injection defense, and tool discovery with server-side execution that preserve your agent's context window and keep reasoning performance.
Lara Translate MCP server vs direct API integration — what's the difference?
A Lara Translate MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling Lara Translate. A Lara Translate MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling Lara Translate at runtime. StackOne provides both.
How does Lara Translate authentication work for AI agents?
Lara Translate authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Lara Translate account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via origin_owner_id.
Are Lara Translate MCP tools vulnerable to prompt injection?
Yes — Lara Translate MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a Lara Translate agent and how do I avoid it?
Context bloat happens when Lara Translate tool schemas and API responses eat your Lara Translate agent's memory, preventing it from reasoning effectively. A single Lara Translate query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my Lara Translate agent can access?
Yes — you can limit which actions your Lara Translate agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Lara Translate MCP server?
Yes — you can create custom agent actions for your Lara Translate MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Lara Translate's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Lara Translate MCP server?
Skip a Lara Translate MCP server if your integration is purely software-to-software — direct Lara Translate API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Lara Translate actions at runtime.
What AI frameworks and AI clients does the StackOne Lara Translate MCP server support?
The StackOne Lara Translate MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.

Put your AI agents to work

All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.