Can I use DeepL as a CLI?

Yes. KosmoKrator exposes a DeepL CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose DeepL through MCP?

Yes. The KosmoKrator MCP gateway can expose selected DeepL tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are DeepL credentials stored?

DeepL credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for DeepL MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

DeepL MCP Integration for Generic MCP Clients

Connect DeepL to Generic MCP Clients through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 5 read 2 write API key auth

Submit DeepL feedback View package source

Connect DeepL to Generic MCP Clients

Connect any stdio-compatible MCP client to local KosmoKrator integration tools.

Register kosmo mcp:serve as the command for a local stdio MCP server. The gateway is local, scoped to this integration, and starts with --write=deny so MCP clients can inspect read-capable tools without receiving write access by default.

DeepL MCP Config for Generic MCP Clients

Start with read-only write policy and expand only for trusted projects.

{
  "mcpServers": {
    "kosmokrator-deepl": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=deepl",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=deepl --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only DeepL instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

DeepL Tools Visible to MCP clients

MCP clients sees stable MCP tool names generated from the DeepL integration catalog.

MCP tool	Source function	Type	Description
`integration__deepl__deepl_translate_text`	`deepl.deepl_translate_text`	Write	Translate text using DeepL. Supports automatic source language detection or explicit source language specification. Returns translated text with detected source language.
`integration__deepl__deepl_list_languages`	`deepl.deepl_list_languages`	Read	List languages supported by DeepL. Returns language codes and names. Filter by type to get only source or target languages.
`integration__deepl__deepl_get_usage`	`deepl.deepl_get_usage`	Read	Get current DeepL API usage. Returns the number of characters translated and the character limit for the current billing period.
`integration__deepl__deepl_list_glossaries`	`deepl.deepl_list_glossaries`	Read	List all glossaries in your DeepL account. Returns glossary IDs, names, language pairs, and entry counts.
`integration__deepl__deepl_get_glossary`	`deepl.deepl_get_glossary`	Read	Get details of a specific DeepL glossary by ID. Returns glossary name, source/target languages, entry count, and creation timestamp.
`integration__deepl__deepl_create_glossary`	`deepl.deepl_create_glossary`	Write	Create a new DeepL glossary. Glossaries define custom translations for specific terms. Entries are tab-separated pairs (source\ttarget), one per line.
`integration__deepl__deepl_get_current_user`	`deepl.deepl_get_current_user`	Read	Get current DeepL account information. Returns usage statistics and account details.

Related DeepL Pages

DeepL CLIUse direct JSON commands instead of MCP discovery. DeepL MCPFull gateway reference and MCP tool names. KosmoKrator for MCP clientsClient-level gateway setup.