mcp-lokalise-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOKALISE_API_TOKEN | Yes | Your Lokalise API token | |
| LOKALISE_PLATFORMS | No | Comma-separated platforms | web |
| LOKALISE_PROJECT_ID | Yes | Your Lokalise project ID |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_lokalise_keyB | Create a new translation key in Lokalise with translations |
| delete_lokalise_keyB | Delete a translation key from Lokalise |
| get_lokalise_keyA | Get a specific translation key from Lokalise by name |
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 3 tools
The three tools are clearly distinct: create, delete, and get are non-overlapping operations on translation keys.
All tools follow the exact pattern 'verb_lokalise_key' with consistent snake_case naming.
With only 3 tools, the server is very focused but borderline thin for a typical scope; however, it fits a minimal key management surface.
Missing essential operations like updating or listing keys, which creates significant gaps for common workflows.