How do AI agents use Lokalise through Open Connector?

Your user connects Lokalise once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Lokalise tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a Lokalise MCP server?

Yes. Open Connector can serve Lokalise as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Lokalise actions with credentials injected server-side.

Where do Lokalise credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Lokalise integration

Lokalise integration for AI agents.

Lokalise integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Lokalise tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real Lokalise actions, managed and audited.

Your user connects Lokalise once; your agent can then secure AI-agent actions — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants Lokalise access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported Lokalise tools.

109 tools are generated from the published Lokalise catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 109 tools. All published catalog entries are included in this page's server-rendered HTML.

Add members to group: Requires *Admin* right in the team. Requires <code>write_team_groups</code> OAuth access scope.; Team Groups
Add projects to group: Requires *Admin* right in the team. Requires <code>write_team_groups</code> OAuth access scope.; Team Groups
Multi-update: Updates one or more keys in the project. Requires *Manage keys* admin right. Requires <code>write_keys</code> OAuth access scope.; Keys
Create a card: Adds new payment card to user cards. Requires <code>write_payment_cards</code> OAuth access scope.; Payment Cards
Create a group: Creates a group in the team. Requires *Admin* right in the team. If `is_admin` flag is set to `true`, the group would automatically get access to all project languages, overriding supplied `languages` object. Requires <code>write_team_groups</code> OAuth access scope.; Team Groups
Create a project: Creates a new project in the specified team. Requires *Admin* role in the team. Requires <code>write_projects</code> OAuth access scope.; Projects
Create a snapshot: Creates snapshot of the project. Requires *Manage settings* admin right. Requires <code>write_snapshots</code> OAuth access scope.; Snapshots
Create a status: Creates a custom translation status in the project. Requires <code>write_custom_translation_statuses</code> OAuth access scope.; Custom Translation Statuses
Create a task: Creates a task in the project. Requires *Manage tasks* admin right. Keep in mind, that <code>initial_tm_leverage</code> attribute will be empty in server response. It's being calculated after the task is created and this process may take some time. Requires <code>write_tasks</code> OAuth access scope.; Tasks
Create a webhook: Creates a webhook in the project. Requires *Manage settings* admin right. See our <a href="https://docs.lokalise.com/en/articles/3184756-webhooks" target="_blank" rel="noopener noreferrer">documentation</a> for available events and payload examples. Requires <code>write_webhooks</code> OAuth access scope.; Webhooks
Create an order: Creates a translation order. You must have admin privileges in the project you are placing an order in. Requires <code>write_team_orders</code> OAuth access scope.; Orders
Create comments: Adds a set of comments to the key. Requires <code>write_comments</code> OAuth access scope.; Comments
Create contributors: Creates one or more contributors in the project. Requires *Manage contributors* admin right. If `is_admin` flag is set to `true`, the user would automatically get access to all project languages, overriding supplied `languages` object. Attribute `fullname` will be ignored, if the user has already been registered in Lokalise. Requires <code>write_contributors</code> OAuth access scope.; Contributors
Create glossary terms: Creates one or more glossary terms in the project. Requires *Manage glossary* admin right. Requires <code>write_glossary</code> OAuth access scope.; Glossary
Create keys: Creates one or more keys in the project. Requires *Manage keys* admin right. We recommend sending payload in chunks of up to 500 keys per request. Requires <code>write_keys</code> OAuth access scope.; Keys
Create languages: Creates one or more languages in the project. Requires *Manage languages* admin right. The `language_iso` is the identifer of one of the system languages. You are only required to include the `language_iso` attribute, however you may override the default language code, language name and plural forms as well. Requires <code>write_languages</code> OAuth access scope.; Languages
Create screenshots: Creates one or more screenshots in the project. Requires *Manage screenshots* admin right. Requires <code>write_screenshots</code> OAuth access scope.; Screenshots
Create a service JWT token: Create a JWT token for working with other services (primarily OTA/mobile SDKs). **Project Type Compatibility:** - ✅ **Software projects** (localization_files) - *Used with mobile SDKs and OTA updates* - ❌ **Documents projects** (paged_documents) - *Not supported* - ❌ **Marketing projects** (content_integration, marketing, marketing_integrations) - *Not supported*; JWT tokens
Create team user billing details: Creates a [Team user billing details](#object-team-user-billing-details) object. Requires <code>write_team_user_billing_details</code> OAuth access scope.; Team User Billing Details
Delete a card: Deletes a payment card from user cards. Requires <code>write_payment_cards</code> OAuth access scope.; Payment Cards
Delete a comment: Deletes a comment from the project. Authenticated user can only delete own comments. Requires <code>write_comments</code> OAuth access scope.; Comments
Delete a contributor: Deletes a user from the project. Requires *Manage contributors* admin right. Requires <code>delete_contributors</code> OAuth access scope.; Contributors
Delete a file: Deletes a file and its associated keys from the project. **Project Type Compatibility:** - ✅ **Documents projects** (paged_documents) - ✅ **Marketing projects** (content_integration, marketing, marketing_integrations) - ❌ **Software projects** (localization_files) - *Not supported* Requires <code>write_files</code> OAuth access scope.; Files
Delete a group: Deletes a group from the team. Requires *Admin* right in the team. Requires <code>write_team_groups</code> OAuth access scope.; Team Groups
Delete a key: Deletes a key from the project. Requires *Manage keys* admin right. **Project Type Compatibility:** - ✅ **Software projects** (localization_files) - ✅ **Marketing projects** (content_integration, marketing, marketing_integrations) - ❌ **Documents projects** (paged_documents) - *Individual key deletion not supported. Keys are managed through file operations.* Requires <code>delete_keys</code> OAuth access scope.; Keys
Delete a language: Deletes a language from the project. Requires *Manage languages* admin right. Requires <code>write_languages</code> OAuth access scope.; Languages
Delete a project: Deletes a project. Requires <code>write_projects</code> OAuth access scope.; Projects
Delete a screenshot: Deletes a screenshot from the project. Requires *Manage screenshots* admin right. Requires <code>write_screenshots</code> OAuth access scope.; Screenshots
Delete a snapshot: Deletes project snapshot. Requires *Manage settings* admin right. Requires <code>write_snapshots</code> OAuth access scope.; Snapshots
Delete a status: Deletes aa custom translation status. Requires <code>write_custom_translation_statuses</code> OAuth access scope.; Custom Translation Statuses
Delete a task: Deletes a task from the project. Requires *Manage tasks* admin right. Requires <code>write_tasks</code> OAuth access scope.; Tasks
Delete a team user: Deletes a user from the team. Requires *Admin* role in the team. Requires <code>write_team_users</code> OAuth access scope.; Team Users
Delete a webhook: Deletes a configured webhook in the project. Requires *Manage settings* admin right. Requires <code>write_webhooks</code> OAuth access scope.; Webhooks
Delete all contributors: Initiates asynchronous deletion of all contributors from the project. Returns a job ID that can be used to track the deletion progress. Requires *Manage contributors* admin right. Requires <code>delete_contributors</code> OAuth access scope. Note: This endpoint returns HTTP 202 (Accepted) upon successful job creation. Use the returned job ID with the job status endpoint to track progress.; Contributors
Delete glossary terms: Deletes all glossary terms from the project. Requires *Manage glossary* admin right. Requires <code>write_glossary</code> OAuth access scope.; Glossary
Delete multiple keys: Deletes multiple keys from the project. Requires *Manage keys* admin right. Requires <code>write_keys</code> OAuth access scope.; Keys
Download files: Exports project files as a .zip bundle. Generated bundle will be uploaded to an Amazon S3 bucket, which will be stored there for 1 month available to download. As the bundle is generated and uploaded you would get a response with the URL to the file. Requires *Download files* admin right. There are two ways to group keys by filenames when you are exporting - either all keys to a single file per language or use the previously assigned filenames. <a href="https://developers.lokalise.com/docs/webhooks-guide" target="`_new`">Learn more</a>. Requires <code>read_files</code> OAuth access scope. *Please note: Starting June 1st, 2025, this endpoint will be limited to projects with under 10,000 key-language pairs, for more details <a href="https://developers.lokalise.com/reference/file-download-limitations" target="`_new`">See our API limits page</a>*; Files
Download files (Async): Starts a project export process. The progress of the process can be tracked using the <a href="https://developers.lokalise.com/reference/list-all-processes">list all processes</a> API endpoint. Once complete, the download URL can be accessed using the <a href="https://developers.lokalise.com/reference/retrieve-a-process">Retrieve process</a> API endpoint. For general details about the Download endpoint, please refer to the <a href="https://developers.lokalise.com/reference/download-files">Download files</a> API endpoint.; Files
Empty a project: Deletes all keys and translations from the project. Requires *Manage settings* admin right. Requires <code>write_projects</code> OAuth access scope.; Projects
Get bulk deletion job status: Retrieves the status of a bulk contributors deletion job. Use the job ID returned from the bulk delete endpoint. Requires <code>read_contributors</code> OAuth access scope.; Contributors
Get team details: Get details of a specific team. Requires <code>read_team_users</code> OAuth access scope.; Teams
Import contributors: Imports contributors from one project to another, copying their roles, permissions, and language assignments. If `contributor_ids` is omitted or empty, all contributors from the source project will be imported. If specified, only the listed contributors will be imported. Requires *Manage contributors* admin right on target project and read access to source project. Requires <code>write_contributors</code> OAuth access scope.; Contributors
List all cards: Lists all user payment cards. Requires <code>read_payment_cards</code> OAuth access scope.; Payment Cards
List all contributors: Lists contributors of the project, including access levels to the project languages. Admins always have read/write access to all languages. Requires <code>read_contributors</code> OAuth access scope.; Contributors
List all files: Lists project files and associated key count. If there are some keys in the project that do not have a file association, they will be returned with filename `__unassigned__`. Requires <code>read_files</code> OAuth access scope.; Files
List all groups: Lists all user groups in the team. Requires <code>read_team_groups</code> OAuth access scope.; Team Groups
List all keys: Lists all keys in the project. This endpoint supports cursor pagination for better performance with large datasets. When using cursor pagination, the response will include a <code>nextCursor</code> value in the response headers when more data is available. Continue making requests with the <code>nextCursor</code> value until no <code>nextCursor</code> is returned, indicating all data has been retrieved. <b>IMPORTANT:</b> We do not provide a content delivery network for your language files. Do not make a request to this endpoint every time a user visits your website/app. Instead, fetch the results from this endpoint from time to time, store them locally, and serve your visitors with static files/your database content. Alternatively, you may use our File Download endpoint with an Amazon S3/Google CouldStorage integration to automatically upload your language files to a bucket of your choice. Requires <code>read_keys</code> OAuth access scope.; Keys
List all orders: Lists all translation orders in the team. Requires <code>read_team_orders</code> OAuth access scope.; Orders
List all permission templates for particular team: List all permission templates for particular team to assign to contributor/group; Permission Templates
List all processes: Retrieves a list of [Queued process](#object-queued-processes) objects. Requires <code>read_background_processes</code> OAuth access scope.; Queued Processes
List all projects: Retrieves a list of projects available to the user, authorized with a token. Requires <code>read_projects</code> OAuth access scope.; Projects
List all providers: Lists all translation providers. Requires <code>read_team_orders</code> OAuth access scope.; Translation Providers
List all screenshots: Retrieves a list of screenshots from the project. Requires <code>read_screenshots</code> OAuth access scope.; Screenshots
List all segments for key language: Retrieves a list of key segment items.; Segments
List all snapshots: Retrieves a list of project snapshots. Requires *Manage settings* admin right. Requires <code>read_snapshots</code> OAuth access scope.; Snapshots
List all statuses: Lists all custom translation statuses in the project. Requires <code>read_custom_translation_statuses</code> OAuth access scope.; Custom Translation Statuses
List all tasks: Lists all tasks in the project. Requires <code>read_tasks</code> OAuth access scope.; Tasks
List all team users: Lists all team users. Requires *Admin* role in the team. Requires <code>read_team_users</code> OAuth access scope.; Team Users
List all teams: Lists all teams available to the user. Requires <code>read_team_users</code> OAuth access scope.; Teams
List all translations: Retrieves a list of project translation items, ungrouped. This endpoint supports cursor pagination for better performance with large datasets. When using cursor pagination, the response will include a <code>nextCursor</code> value in the response headers when more data is available. Continue making requests with the <code>nextCursor</code> value until no <code>nextCursor</code> is returned, indicating all data has been retrieved. You may want to request [Keys](#resource-keys) resource in order to get the structured key/translation pairs for all languages. Requires <code>read_translations</code> OAuth access scope.; Translations
List all webhooks: Retrieves a list of configured webhooks. Requires *Manage settings* admin right. Requires <code>read_webhooks</code> OAuth access scope.; Webhooks
List glossary terms: Retrieves a list of glossary terms. This endpoint supports cursor pagination for better performance with large datasets. When using cursor pagination, the response will include a <code>nextCursor</code> value in the metadata when more data is available. Continue making requests with the <code>nextCursor</code> value until no <code>nextCursor</code> is returned, indicating all data has been retrieved. Requires <code>read_glossary</code> OAuth access scope.; Glossary
List key comments: Retrieves a list of all comments for a key. Requires <code>read_comments</code> OAuth access scope.; Comments
List project comments: Retrieves a list of all comments in the project. Requires <code>read_comments</code> OAuth access scope.; Comments
List project languages: Retrieves a list of project languages. Requires <code>read_languages</code> OAuth access scope.; Languages
List project translation memories: Retrieves a list of translation memories enabled for the project. Requires <code>read_projects</code> OAuth access scope.; Translation Memories
List system languages: Retrieves a list of system languages. Requires <code>read_languages</code> OAuth access scope.; Languages
Regenerate a webhook secret: Regenerate a webhook secret. Requires *Manage settings* admin right. Requires <code>write_webhooks</code> OAuth access scope.; Webhooks
Remove members from group: Requires *Admin* right in the team. Requires <code>write_team_groups</code> OAuth access scope.; Team Groups
Remove projects from group: Requires *Admin* right in the team. Requires <code>write_team_groups</code> OAuth access scope.; Team Groups
Restore a snapshot: Restores project snapshot to a project copy. Requires *Manage settings* admin right and *Admin* role in the team. Requires <code>write_snapshots</code> OAuth access scope.; Snapshots
Retrieve a basic user data: Retrieves a [User](#object-users) object. Not available via OAuth token. Available via S2S.; Users
Retrieve a card: Retrieves a [Payment card](#object-cards) object. Requires <code>read_payment_cards</code> OAuth access scope.; Payment Cards
Retrieve a comment: Retrieves a [Comment](#object-comments) object. Requires <code>read_comments</code> OAuth access scope.; Comments
Retrieve a contributor: Retrieves a [Contributor](#object-contributors) object. Requires <code>read_contributors</code> OAuth access scope.; Contributors
Retrieve a glossary term: Retrieves a [Glossary Term](#object-glossary-terms) object. Requires <code>read_glossary</code> OAuth access scope.; Glossary
Retrieve a group: Retrieves a [User group](#object-user-groups) object. Requires <code>read_team_groups</code> OAuth access scope.; Team Groups
Retrieve a key: Retrieves a [Key](#object-keys) object. Requires <code>read_keys</code> OAuth access scope.; Keys
Retrieve a language: Retrieves a [Language](#object-languages) object. Requires <code>read_languages</code> OAuth access scope.; Languages
Retrieve a process: Retrieves a [Queued process](#object-queued-processes) object with an additional <code>details</code> field containing information for a specific process type. Requires <code>read_background_processes</code> OAuth access scope.; Queued Processes
Retrieve a project: Retrieves a [Project](#object-projects) object. Requires <code>read_projects</code> OAuth access scope.; Projects
Retrieve a provider: Retrieves a [Translation provider](#object-providers) object with tiers and available language pairs. Requires <code>read_team_orders</code> OAuth access scope.; Translation Providers
Retrieve a screenshot: Retrieves a [Screenshot](#object-screenshots) object. Requires <code>read_screenshots</code> OAuth access scope.; Screenshots
Retrieve a segment for key language: Retrieves a [Segment](#object-segments) object.; Segments
Retrieve a status: Retrieves a [Custom Translation Status](#object-translation-statuses) object. Requires <code>read_custom_translation_statuses</code> OAuth access scope.; Custom Translation Statuses
Retrieve a task: Retrieves a [Task](#object-tasks) object. Requires <code>read_tasks</code> OAuth access scope.; Tasks
Retrieve a team user: Retrieves a [Team user](#object-team-users) object. Requires *Admin* role in the team. Requires <code>read_team_users</code> OAuth access scope.; Team Users
Retrieve a translation: Retrieves a [Translation](#object-translations) object. Requires <code>read_translations</code> OAuth access scope.; Translations
Retrieve a webhook: Retrieves a [Webhook](#object-webhooks) object. Requires *Manage settings* admin right. Requires <code>read_webhooks</code> OAuth access scope.; Webhooks
Retrieve an order: Retrieves an [Order](#object-orders) object. Requires <code>read_team_orders</code> OAuth access scope.; Orders
Retrieve available colors: Retrieves an array of available colors that can be assigned to custom translation statuses. Requires <code>read_custom_translation_statuses</code> OAuth access scope.; Custom Translation Statuses
Retrieve a contributor representing user sending a query: Retrieves a [Contributor](#object-contributors) object. Gets combined permissions from contributor and a group. Requires <code>read_contributors</code> OAuth access scope.; Contributors
Retrieve task usage metrics: Retrieves usage metrics for a specific task. Data is available from November 3rd 2025 onwards. Requires <code>read_tasks</code> OAuth access scope.; Tasks
Retrieve team user billing details: Retrieve a [Team user billing details](#object-team-user-billing-details) object. Requires <code>read_team_user_billing_details</code> OAuth access scope.; Team User Billing Details
Update a contributor: Updates the properties of a contributor. Requires *Manage contributors* admin right. If you want to give an existing contributor access to a new language, you must specify full `languages` array, including the previously added languages as well. You can pass role_id and permissions will be updated from permission template accordingly, in this case admin_rights param will be ignored Requires <code>write_contributors</code> OAuth access scope.; Contributors
Update a group: Updates the properties of a group. Requires *Admin* right in the team. Requires <code>write_team_groups</code> OAuth access scope.; Team Groups
Update a key: Updates the properties of a key and it's associated objects. Requires *Manage keys* admin right. Requires <code>write_keys</code> OAuth access scope.; Keys
Update a language: Updates the properties of a language. Requires *Manage languages* admin right. Requires <code>write_languages</code> OAuth access scope.; Languages
Update a project: Updates the details of a project. Requires *Manage settings* admin right. Requires <code>write_projects</code> OAuth access scope.; Projects
Update a screenshot: Updates the properties of a screenshot. Requires *Manage screenshots* admin right. Requires <code>write_screenshots</code> OAuth access scope.; Screenshots
Update a segment: Updates a segment.; Segments
Update a status: Updates the custom translation status. Requires <code>write_custom_translation_statuses</code> OAuth access scope.; Custom Translation Statuses
Update a task: Updates the properties of a task. Requires *Manage tasks* admin right. Requires <code>write_tasks</code> OAuth access scope.; Tasks
Update a team user: Updates the role of a team user. Requires *Admin* role in the team. Requires <code>write_team_users</code> OAuth access scope.; Team Users
Update a translation: Updates a translation. Alternatively, use the <a href="/reference/bulk-update">Multi-key update</a> endpoint to update translations. Requires <code>write_translations</code> OAuth access scope.; Translations
Update a webhook: Updates a configured webhook in the project. Requires *Manage settings* admin right. Requires <code>write_webhooks</code> OAuth access scope.; Webhooks
Update glossary terms: Updates one or more glossary terms in the project. Requires *Manage glossary* admin right. Requires <code>write_glossary</code> OAuth access scope.; Glossary
Update team user billing details: Updates a [Team user billing details](#object-team-user-billing-details) object. Requires <code>write_team_user_billing_details</code> OAuth access scope.; Team User Billing Details
Upload a file: Queues a localization file for import and returns a <code>202</code> or <code>302</code> response along with a <a href="#object-queued-processes">Queued process</a> object. <a href="https://docs.lokalise.com/developer-docs/uploading-files" target="`_new`">Learn more</a>. Requires *Upload files* admin right. <a href="https://docs.lokalise.com/en/collections/2909229-supported-file-formats" target=_new>Supported file types</a>. Please note that the <code>302</code> response code is not currently used, but in the future it will be returned if the same file is already in the upload queue. Requires <code>write_files</code> OAuth access scope.; Files

FAQ

Lokalise integration, answered

How do AI agents use Lokalise through Open Connector?: Your user connects Lokalise once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Lokalise tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Lokalise MCP server?: Yes. Open Connector can serve Lokalise as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Lokalise actions with credentials injected server-side.
Where do Lokalise credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Lokalise — keep the keys.

Open source, self-hostable, with Lokalise credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →