What can you do with the Azure Translator integration?

LiveContext exposes 15 operations on Azure Translator, covering batch, document, dictionary and language. Common uses include job dashboard, error recovery and job monitoring.

What are the Azure Translator API rate limits?

Azure Translator documents 100 requests per second. Limits vary by subscription tier (Free, S1, S2, etc.) Limits are set by Azure Translator and can depend on your plan.

LiveContext

All integrations

Azure Translator integration

Microsoft Cognitive Services Translator is a cloud-based neural machine translation service that enables real-time text translation, language detection, transliteration, dictionary lookups, and document translation. Supports 100+ languages with high accuracy for global multilingual applications, content localization, and cross-language communication.

15 toolsAPI keyAPI docs

Connect Azure Translator How integrations work

Common Azure Translator use cases

job dashboard
error recovery
job monitoring
content routing
file validation
language learning
language picker UI
website localization
document localization
Japanese romanization

What you can do with Azure Translator

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Batch, 4 operations

DELETEcancel_batch_translation
Cancels a batch translation job that is running or queued. Documents already translated remain available; pending documents are cancelled and not charged.
GETget_all_batches_status
Lists all batch translation jobs for the account with pagination support. Returns job IDs, statuses, creation times, and document counts for each batch. Supports filtering by status, IDs, and date ranges, and sorting.
GETget_batch_status
Retrieves the current status of a batch translation job by ID. Returns overall job status, document counts by state (NotStarted, Running, Succeeded, Failed, Cancelled), progress percentage, and any error information.
POSTstart_batch_translation
Initiates an asynchronous batch translation job for multiple documents in Azure Blob Storage. Specify source container with documents and target containers for each language. Returns a job ID for status tracking.

Document, 3 operations

GETget_documents_status
Retrieves the translation status of all documents within a batch job. Returns document IDs, source/target paths, status, character counts, and error details for each document.
GETget_document_status
Retrieves the translation status of a specific document within a batch job. Returns the document path, status, target language, progress percentage, and character charge count.
POSTtranslate_document
Translates a single document synchronously while preserving the original formatting, layout, and structure. Supports PDF, DOCX, PPTX, XLSX, HTML, TXT, and other formats. Returns the translated document directly.

Dictionary, 2 operations

POSTdictionary_examples
Retrieves contextual example sentences demonstrating how a word and its translation are used in parallel texts. Input requires both the source term and target translation (from dictionary_lookup). Returns bilingual sentence pairs with the relevant...
POSTdictionary_lookup
Performs bilingual dictionary lookup to find alternative translations for words or short phrases. Returns multiple translation options with part-of-speech tags (NOUN, VERB, ADJ, etc.), confidence scores, and back-translations showing how frequentl...

Language, 2 operations

POSTdetect_language
Detects the language of input text using Azure Translator. Returns the detected language code with a confidence score (0-1), flags indicating whether translation and transliteration are supported for the detected language, and alternative language...
GETget_languages
Retrieves the complete list of languages supported by Azure Translator. Returns three categories: translation (100+ languages for text translation), transliteration (languages that support script conversion), and dictionary (language pairs for bil...

Format, 1 operation

GETget_supported_formats
Retrieves the list of document and glossary formats supported by Document Translation. Returns format details including extensions, content types, and version information.

Sentence, 1 operation

POSTbreak_sentence
Identifies sentence boundaries in text and returns the character length of each sentence. Supports automatic language detection. Useful for splitting large texts into translatable segments or analyzing document structure.

Text, 1 operation

POSTtransliterate
Converts text from one writing script to another within the same language using Azure Translator. Common use cases include romanization (converting Japanese/Chinese/Arabic to Latin letters) and script normalization. Returns the converted text in t...

Translation, 1 operation

POSTtranslate_text
Translates text from source language to one or more target languages using Azure's neural machine translation. Supports automatic language detection when 'from' is omitted, multiple target languages in a single request (to=de&to=fr), HTML content ...

Azure Translator API rate limits

100 requests per second

Limits vary by subscription tier (Free, S1, S2, etc.)

These are the limits Azure Translator documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Azure Translator documentation for current values.

Use Azure Translator from Claude Code, Cursor or Codex

Connect Azure Translator in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Azure Translator operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Azure Translator

Create your workspace
Sign up free. Nothing to install.
Connect Azure Translator once
Add your Azure Translator connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Azure Translator integration FAQ

What can you do with the Azure Translator integration?: LiveContext exposes 15 operations on Azure Translator, covering batch, document, dictionary and language. Common uses include job dashboard, error recovery and job monitoring.
What are the Azure Translator API rate limits?: Azure Translator documents 100 requests per second. Limits vary by subscription tier (Free, S1, S2, etc.) Limits are set by Azure Translator and can depend on your plan.