Bring Localization
to CrewAI
Learn how to connect Lokalise to CrewAI and start using 13 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
What is the Lokalise MCP Server?
Connect your Lokalise account to any AI agent and take full control of your translation and localization workflows through natural conversation.
What you can do
- Project Management — List all translation projects, fetch detailed project metadata, and create new projects directly from the API
- Key Management — Query translation keys with filters by platform, tags, or filenames, plus create and update keys programmatically
- Translation Operations — Fetch translations for any key, add new translations with review/fuzzy flags, and manage multi-language content
- File Import/Export — Upload localization files (JSON, YAML, XLIFF) and generate download bundles in any supported format
- Team & Orders — List team members and their roles, plus inspect professional translation orders
How it works
1. Subscribe to this server
2. Enter your Lokalise API Token
3. Start managing your localization workflows from Claude, Cursor, or any MCP-compatible client
No more jumping between the Lokalise web console and your codebase. Your AI acts as a dedicated localization coordinator.
Who is this for?
- Developers — instantly create translation keys, push new strings, and pull localized files without leaving the IDE
- Product Managers — check translation progress across languages, review key counts, and monitor team activity
- Localization Teams — automate bulk uploads, generate export bundles, and manage translation orders programmatically
Built-in capabilities (13)
Add translations to one or more keys
Create translation keys in a Lokalise project
Create a new Lokalise project
Generate a download bundle of translations
Get details of a specific Lokalise project
List translation keys in a Lokalise project
List languages in a Lokalise project
List translation orders in your Lokalise account
List all Lokalise projects
List all team members in your Lokalise account
List translations for a key in a Lokalise project
Update an existing translation key
Upload a localization file to a Lokalise project
Why CrewAI?
When paired with CrewAI, Lokalise becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Lokalise tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Lokalise in CrewAI
Lokalise and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Lokalise to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Lokalise in CrewAI
The Lokalise MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 13 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Lokalise for CrewAI
Every tool call from CrewAI to the Lokalise MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
What kind of Lokalise API token do I need for this integration?
You need a Personal Access Token from your Lokalise account. Go to your profile settings, find the API Tokens section, and generate a new token with read/write access to projects. Keep this token secure as it grants full API access to your account.
How do I add a new translation key to my Lokalise project via the AI agent?
Use the create_key action with the project ID, key name (e.g., homepage.welcome.title), and optionally specify platforms, tags, and a description. The key will be created with the base language placeholder ready for translation.
Can I export all my translations in a specific format like JSON or YAML?
Yes! Use the download_file action and specify the format parameter (e.g., json, yml, xliff, strings, xml). You can also filter by specific languages or filenames to generate targeted export bundles.
Is it possible to add translations programmatically for multiple languages at once?
Yes. The add_translation action supports adding translations for one or more keys at once. You can also mark translations as fuzzy or reviewed to indicate their quality status in the workflow.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.