Lokalise

@lokalise list all untranslated keys in the mobile-app project for German and French, then show me which ones are marked as high priority

Found 47 untranslated keys across German (de) and French (fr) in mobile-app. High-priority keys include: onboarding.welcome_title, checkout.payment_error, settings.privacy_policy_link, and 8 others. German has 28 missing translations (12 high-priority), French has 19 (4 high-priority). All high-priority keys were flagged in the last sprint and are blocking the Q2 release branch. The full list includes key IDs, platform tags, and last-modified timestamps for triage.

This example combines list-keys filtering with the AI's ability to parse priority metadata. Requires a read token with project access. Large projects may need pagination; the MCP returns one cursor page at a time, so follow-up prompts can fetch additional results if the count exceeds the page limit.

@lokalise create keys for error.network_timeout, error.server_unavailable, and error.invalid_input in the web-dashboard project with English placeholders and tag them as 'error-handling'

Created 3 new keys in web-dashboard with base English text and the 'error-handling' tag. Key IDs: 184729301 (error.network_timeout), 184729302 (error.server_unavailable), 184729303 (error.invalid_input). Each key is now visible to translators in all configured project languages. Note that translations for the 6 non-English languages (es, fr, de, ja, pt, zh) are still empty and will require manual input or machine translation.

Demonstrates bulk key creation, a common workflow when scaffolding new features. Requires a read/write token and Manage Keys permission. The MCP can create up to 500 keys per call, but each new key immediately appears in all project languages as untranslated, so coordinate with your localization team before running large batches.

@lokalise pull the last 20 audit log events for our team and summarize any key deletions or permission changes that happened in the past week

Retrieved 20 recent audit events (OCSF 1.3.0 format). In the past 7 days: 2 key deletions by user emma@company.com on March 14 (keys: legacy.unused_banner, promo.expired_offer), and 1 permission change on March 12 where admin role was granted to dev@company.com for the mobile-app project. No other destructive actions detected. All events include actor email, timestamp, and affected resource IDs for compliance tracking.

Audit log access requires a team admin token and a Lokalise plan that includes this feature (Enterprise or higher). The MCP returns one page at a time; for compliance or security investigations spanning months, you'll need to paginate. This example shows how the AI can filter and summarize high-risk events from raw OCSF logs.

How product teams scope localization work with this MCP

A product manager and two designers plan a Q2 feature that will add 80 new UI strings across 12 languages. They need to estimate localization cost and timeline before the kickoff. The Lokalise MCP lets them list current project languages, count existing keys by branch, and pull recent translation velocity from audit logs—all from a shared AI workspace doc. This scenario works when your team runs quarterly planning cycles and localization budget is a first-class constraint. If your product ships in 1-3 languages or you have a dedicated localization PM who owns the roadmap, the MCP's project-level queries are overkill. For cross-functional teams that need to answer 'how much will this cost to translate' during the planning phase, this MCP turns a 30-minute Lokalise spelunking session into a 5-minute AI query.