DeepL MCP integration for AI agents.
Connect AI agents to DeepL through 3 structured actions, including get usage, translate text, and list supported languages. Review authentication, inputs, wo…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the DeepL integration exposes
The DeepL Agent App exposes 3 provider-backed actions for ai and productivity work. Its current contract lets an authorized agent fetch the current deepl api usage and quota counters for the connected api key, translate one or more text items with deepl and return the normalized translation results, and list the deepl source or target languages currently supported by the translation api. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected DeepL account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real DeepL capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_usageREADFetch the current DeepL API usage and quota counters for the connected API key.
translate_textREVIEWTranslate one or more text items with DeepL and return the normalized translation results.
INPUTS: texts / target_lang / source_lang / context / formality
list_supported_languagesREADList the DeepL source or target languages currently supported by the translation API.
INPUTS: type
INPUT CONTRACTS
Know what the action needs before it runs.
translate_text
textsREQUIRED- The text items to translate in a single DeepL request.
target_langREQUIRED- The target language code for the translation.
source_langOPTIONAL- The source language code to force upstream.
contextOPTIONAL- Optional context that guides translation without being translated itself.
formalityOPTIONAL- The DeepL formality preference for supported target languages.
list_supported_languages
typeOPTIONAL- Whether to list source or target languages.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Usage
Fetch the current DeepL API usage and quota counters for the connected API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_usageVerify with List Supported Languages
List the DeepL source or target languages currently supported by the translation API. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_supported_languagesSAFETY BOUNDARY
Operate DeepL with explicit limits
- Authorize DeepL with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned DeepL data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in DeepL rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the DeepL task completed successfully.
CONNECTION MODEL
API key
DeepL API key sent with the DeepL-Auth-Key authorization scheme. Find and manage it in the API Keys & Limits tab of your DeepL API account: https://developers.deepl.com/docs/getting-started/managing-api-keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by DeepL.