Skip to content
actionlake
Start free

Connectors · Marketing & media

Lokalise MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Lokalise and the rest of your systems. It gives your agent 114 Lokalise actions (54 reads, 39 writes and 21 that wait for a confirmation) and holds the Lokalise credential itself, so the agent never does. It paces Lokalise's limits and records every call.

Connect Lokalise freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "lokalise.projects.list",  intent: "check which Lokalise account is connected"}# List all projects · read · 1 upstream call
  • 114actionsin one signed file
  • 54readlook, never change
  • 39writecreate and update
  • 21wait for a yesdestructive, confirmed first

Set up

Connect Lokalise in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Lokalise.

    API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • api_tokenLokalise API token: in Lokalise, click your avatar > Profile settings > API tokens > Generate new token (read and…
    account { op: "connections.requirements", service: "lokalise" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "lokalise.projects.list" }# list all projects · read · 1 upstream callcheck { action: "lokalise.tasks.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Lokalise at a glance

Sign-in
API key. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
api_token
Limits we pace to
6 calls a second, per connection
API covered
Lokalise API v2 (OpenAPI 3.0.3)api.lokalise.com/api2
Built from
Lokalise's documentation, read 23 October 2026developers.lokalise.comdevelopers.lokalise.comdevelopers.lokalise.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
47 of 54 reads, for up to 2 minutes; a write clears what it affects
Shared entities
5, so ask can line Lokalise up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Lokalise.

114 actions in 28 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 54readlook, never change
  • 39writecreate and update
  • 21destructivewait for a confirmation

  1. Contributors

    9

    4 read · 3 write · 2 destructive

    List all contributors · Create contributors · Retrieve a contributor · Update a contributor

  2. Groups

    9

    2 read · 4 write · 3 destructive

    List all groups · Create a group · Retrieve a group · Update a group

  3. Keys

    7

    2 read · 3 write · 2 destructive

    Create keys · List all keys · Retrieve a key · Update a key

  4. Branches

    6

    2 read · 3 write · 1 destructive

    Create a branch · List all branches · Retrieve a branch · Merge a branch

  5. Projects

    6

    2 read · 2 write · 2 destructive

    List all projects · Create a project · Retrieve a project · Update a project

  6. Tasks

    6

    3 read · 2 write · 1 destructive

    List all tasks · Create a task · Retrieve a task · Update a task

  7. Translation statuses

    6

    3 read · 2 write · 1 destructive

    Create a status · List all statuses · Retrieve available colors · Retrieve a status

  8. Webhooks

    6

    2 read · 3 write · 1 destructive

    Create a webhook · List all webhooks · Update a webhook · Retrieve a webhook

20 more areas · 59 actions
  • Comments 5
  • Files 5
  • Glossary terms 5
  • Languages 5
  • Screenshots 5
  • Snapshots 4
  • Team users 4
  • Billing details 3
  • Orders 3
  • Payment cards 3
  • Segments 3
  • Translations 3
  • Processes 2
  • Teams 2
  • Translation providers 2
  • JWT 1
  • Permission templates 1
  • System languages 1
  • Translation memories 1
  • Users 1

Top actions

The Lokalise API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 32 of Lokalise's 32 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
lokalise.tasks.listList all tasksList all tasks.readwork.task.list122 connectors
lokalise.team_users.listList all team usersList all team users.readidentity.user.list474 connectors
lokalise.projects.listList all projectsList all projects.readwork.project.list109 connectors
lokalise.tasks.createCreate a taskCreate a task.writework.task.create127 connectors
lokalise.projects.createCreate a projectCreate a project.writework.project.create102 connectors
lokalise.groups.listList all groupsList all groups.readidentity.group.list262 connectors
lokalise.team_users.getRetrieve a team userRetrieve a team user.readidentity.user.get399 connectors
lokalise.tasks.deleteDelete a taskDelete a task.destructivework.task.delete107 connectors
lokalise.groups.createCreate a groupCreate a group.writeidentity.group.create205 connectors
lokalise.contributors.listList all contributorsList all contributors.readthis connector
lokalise.webhooks.createCreate a webhookCreate a webhook.writeautomation.webhook.create209 connectors
lokalise.webhooks.listList all webhooksList all webhooks.readautomation.webhook.list202 connectors

Try it

Prompts to paste into Claude.

Each one names the Lokalise actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Which Lokalise tasks are overdue, and who owns each one?

    callslokalise.tasks.list

  2. Writewrite

    Create a task in Lokalise. Show me exactly what you will send before you save it.

    callslokalise.tasks.create

Governance for Lokalise

Destructive actions wait for a yes.

21 Lokalise actions are destructive. These are all of them:

  • Delete a tasklokalise.tasks.delete
  • Delete a projectlokalise.projects.delete
  • Delete a team userlokalise.team_users.delete
  • Delete a grouplokalise.groups.delete
  • Delete a webhooklokalise.webhooks.delete
  • Delete a keylokalise.keys.delete
  • Delete a filelokalise.files.delete
  • Delete a commentlokalise.comments.delete
  • Delete a languagelokalise.languages.delete
  • Delete a screenshotlokalise.screenshots.delete
  • Delete a contributorlokalise.contributors.delete
  • Delete glossary termslokalise.glossary_terms.delete_many
  • Empty a projectlokalise.projects.empty
  • Delete a branchlokalise.branches.delete
  • Delete multiple keyslokalise.keys.delete_many
  • Delete a snapshotlokalise.snapshots.delete
  • Delete a cardlokalise.payment_cards.delete
  • Remove members from grouplokalise.groups.remove_members
  • Remove projects from grouplokalise.groups.remove_projects
  • Delete all contributorslokalise.contributors.delete_all
  • Delete a statuslokalise.translation_statuses.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dolokalise.tasks.deleteconfirm_policy: human

Delete a task?

intent: the user asked me to delete a task

run suspended · waiting for a named person · key lokalise-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "lokalise-agent",  allowed_actions: ["lokalise.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "lokalise.tasks.delete", approver: "[email protected]" },    { match: "lokalise.projects.delete", approver: "[email protected]" },    { match: "lokalise.team_users.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Lokalise only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Lokalise costs on actionlake.

Every Lokalise action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Lokalise refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 114 Lokalise actions
  • 114actions pageeach page of a long list is one call
  • 47reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Lokalise action.

114 actions by area: the id your agent calls, what it does, and its effect.

Contributors9
  • lokalise.contributors.createCreate contributorswrite
  • lokalise.contributors.deleteDelete a contributordestructive
  • lokalise.contributors.delete_allDelete all contributorsdestructive
  • lokalise.contributors.getRetrieve a contributorread
  • lokalise.contributors.get_jobGet bulk deletion job statusread
  • lokalise.contributors.get_meRetrieve a contributor representing user sending a queryread
  • lokalise.contributors.importImport contributorswrite
  • lokalise.contributors.listList all contributorsread
  • lokalise.contributors.updateUpdate a contributorwrite
Groups9
  • lokalise.groups.add_membersAdd members to groupwrite
  • lokalise.groups.add_projectsAdd projects to groupwrite
  • lokalise.groups.createCreate a groupwrite
  • lokalise.groups.deleteDelete a groupdestructive
  • lokalise.groups.getRetrieve a groupread
  • lokalise.groups.listList all groupsread
  • lokalise.groups.remove_membersRemove members from groupdestructive
  • lokalise.groups.remove_projectsRemove projects from groupdestructive
  • lokalise.groups.updateUpdate a groupwrite
Keys7
  • lokalise.keys.bulk_updateMulti-updatewrite
  • lokalise.keys.createCreate keyswrite
  • lokalise.keys.deleteDelete a keydestructive
  • lokalise.keys.delete_manyDelete multiple keysdestructive
  • lokalise.keys.getRetrieve a keyread
  • lokalise.keys.listList all keysread
  • lokalise.keys.updateUpdate a keywrite
Branches6
  • lokalise.branches.createCreate a branchwrite
  • lokalise.branches.deleteDelete a branchdestructive
  • lokalise.branches.getRetrieve a branchread
  • lokalise.branches.listList all branchesread
  • lokalise.branches.mergeMerge a branchwrite
  • lokalise.branches.updateUpdate a branchwrite
Projects6
  • lokalise.projects.createCreate a projectwrite
  • lokalise.projects.deleteDelete a projectdestructive
  • lokalise.projects.emptyEmpty a projectdestructive
  • lokalise.projects.getRetrieve a projectread
  • lokalise.projects.listList all projectsread
  • lokalise.projects.updateUpdate a projectwrite
Tasks6
  • lokalise.tasks.createCreate a taskwrite
  • lokalise.tasks.deleteDelete a taskdestructive
  • lokalise.tasks.getRetrieve a taskread
  • lokalise.tasks.get_usage_metricsRetrieve task usage metricsread
  • lokalise.tasks.listList all tasksread
  • lokalise.tasks.updateUpdate a taskwrite
Translation statuses6
  • lokalise.translation_statuses.createCreate a statuswrite
  • lokalise.translation_statuses.deleteDelete a statusdestructive
  • lokalise.translation_statuses.getRetrieve a statusread
  • lokalise.translation_statuses.listList all statusesread
  • lokalise.translation_statuses.list_colorsRetrieve available colorsread
  • lokalise.translation_statuses.updateUpdate a statuswrite
Webhooks6
  • lokalise.webhooks.createCreate a webhookwrite
  • lokalise.webhooks.deleteDelete a webhookdestructive
  • lokalise.webhooks.getRetrieve a webhookread
  • lokalise.webhooks.listList all webhooksread
  • lokalise.webhooks.regenerate_secretRegenerate a webhook secretwrite
  • lokalise.webhooks.updateUpdate a webhookwrite
Comments5
  • lokalise.comments.createCreate commentswrite
  • lokalise.comments.deleteDelete a commentdestructive
  • lokalise.comments.getRetrieve a commentread
  • lokalise.comments.listList key commentsread
  • lokalise.comments.list_projectList project commentsread
Files5
  • lokalise.files.deleteDelete a filedestructive
  • lokalise.files.downloadDownload filesread
  • lokalise.files.download_asyncDownload files (Async)read
  • lokalise.files.listList all filesread
  • lokalise.files.uploadUpload a filewrite
Glossary terms5
  • lokalise.glossary_terms.createCreate glossary termswrite
  • lokalise.glossary_terms.delete_manyDelete glossary termsdestructive
  • lokalise.glossary_terms.getRetrieve a glossary termread
  • lokalise.glossary_terms.listList glossary termsread
  • lokalise.glossary_terms.update_manyUpdate glossary termswrite
Languages5
  • lokalise.languages.createCreate languageswrite
  • lokalise.languages.deleteDelete a languagedestructive
  • lokalise.languages.getRetrieve a languageread
  • lokalise.languages.listList project languagesread
  • lokalise.languages.updateUpdate a languagewrite
Screenshots5
  • lokalise.screenshots.createCreate screenshotswrite
  • lokalise.screenshots.deleteDelete a screenshotdestructive
  • lokalise.screenshots.getRetrieve a screenshotread
  • lokalise.screenshots.listList all screenshotsread
  • lokalise.screenshots.updateUpdate a screenshotwrite
Snapshots4
  • lokalise.snapshots.createCreate a snapshotwrite
  • lokalise.snapshots.deleteDelete a snapshotdestructive
  • lokalise.snapshots.listList all snapshotsread
  • lokalise.snapshots.restoreRestore a snapshotwrite
Team users4
  • lokalise.team_users.deleteDelete a team userdestructive
  • lokalise.team_users.getRetrieve a team userread
  • lokalise.team_users.listList all team usersread
  • lokalise.team_users.updateUpdate a team userwrite
Billing details3
  • lokalise.billing_details.createCreate team user billing detailswrite
  • lokalise.billing_details.getRetrieve team user billing detailsread
  • lokalise.billing_details.updateUpdate team user billing detailswrite
Orders3
  • lokalise.orders.createCreate an orderwrite
  • lokalise.orders.getRetrieve an orderread
  • lokalise.orders.listList all ordersread
Payment cards3
  • lokalise.payment_cards.deleteDelete a carddestructive
  • lokalise.payment_cards.getRetrieve a cardread
  • lokalise.payment_cards.listList all cardsread
Segments3
  • lokalise.segments.getRetrieve a segment for key languageread
  • lokalise.segments.listList all segments for key languageread
  • lokalise.segments.updateUpdate a segmentwrite
Translations3
  • lokalise.translations.getRetrieve a translationread
  • lokalise.translations.listList all translationsread
  • lokalise.translations.updateUpdate a translationwrite
Processes2
  • lokalise.processes.getRetrieve a processread
  • lokalise.processes.listList all processesread
Teams2
  • lokalise.teams.getGet team detailsread
  • lokalise.teams.listList all teamsread
Translation providers2
  • lokalise.translation_providers.getRetrieve a providerread
  • lokalise.translation_providers.listList all providersread
JWT1
  • lokalise.jwt.createCreate a service JWT tokenwrite
Permission templates1
  • lokalise.permission_templates.listList all permission templates for particular teamread
System languages1
  • lokalise.system_languages.listList system languagesread
Translation memories1
  • lokalise.translation_memories.listList project translation memoriesread
Users1
  • lokalise.users.getRetrieve a basic user dataread

Questions

The Lokalise MCP server, answered.

Is there a Lokalise MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 114 Lokalise actions across contributors, groups, keys and branches, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Lokalise.

What do I need to connect Lokalise?

Lokalise API token: in Lokalise, click your avatar > Profile settings > API tokens > Generate new token (read and…. The free call account { op: "connections.requirements", service: "lokalise" } lists exactly what to paste.

Can an AI agent delete or change things in Lokalise?

Only if its key allows it, and only with an explicit confirmation. 21 Lokalise actions are destructive, including delete a task, delete a project and delete a team user. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Lokalise API limit?

actionlake paces every call to the limits in the Lokalise service file: 6 calls a second per connection. Repeated reads are answered from cache (47 Lokalise actions can be), which never reaches Lokalise.

What does a Lokalise action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (114 Lokalise actions page). Cache hits, searches, dry runs and calls Lokalise refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Lokalise API does it cover?

The Lokalise API v2 (OpenAPI 3.0.3) at api.lokalise.com/api2. It is built from Lokalise's documentation as read on 23 October 2026. 114 actions in 28 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Lokalise data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 2 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Lokalise credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like Lokalise

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Lokalise; the name is the vendor's own. Counts are from the Lokalise service file, version 1.0.0.

Give your agent Lokalise today.

Connect Lokalise freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.