Lokalise MCP Tool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOKALISE_API_KEY | Yes | The API key for your Lokalise account, used to authenticate requests. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_lokalise_keysC | Add multiple translation keys to a Lokalise project using structured input |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as adding translation keys to a Lokalise project.
A single tool inherently has perfect naming consistency. The tool name 'add_lokalise_keys' follows a clear verb_noun pattern and is descriptive of its function.
A single tool for a Lokalise MCP server is too few for typical translation management workflows. Lokalise involves operations like creating, updating, deleting, and fetching keys or translations, so one tool feels incomplete and thin for the domain.
The tool set is severely incomplete for Lokalise translation management. It only supports adding keys, missing essential operations like retrieving, updating, or deleting keys, managing translations, or handling projects, which will cause significant agent failures.