texterify-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEXTERIFY_AUTH_EMAIL | Yes | Your Texterify account email | |
| TEXTERIFY_PROJECT_ID | No | UUID of the project to operate on (can be provided per-tool or via env) | |
| TEXTERIFY_API_VERSION | No | API version (default: v1) | v1 |
| TEXTERIFY_AUTH_SECRET | Yes | Your Texterify API secret / access token | |
| TEXTERIFY_API_BASE_URL | No | API base URL (default: https://app.texterify.com/api) | https://app.texterify.com/api |
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 |
|---|---|
No tools | |
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 7 tools
Most tools have distinct purposes, but there is some overlap between create_key and create_key_with_translations, as both create keys with slightly different workflows. The descriptions clarify that one is atomic with translations while the other is just the key, but an agent might still be confused about which to use initially. Other tools like list_keys, get_key, and update_key are clearly differentiated.
All tool names follow a consistent verb_noun pattern (e.g., create_key, list_keys, update_key), with clear and predictable naming. There are no deviations in style or convention, making it easy for an agent to understand the action and target resource at a glance.
With 7 tools, this server is well-scoped for managing translation keys and projects in Texterify. It covers core operations like creation, retrieval, listing, and updates, without being overly complex or too sparse. The count aligns well with the domain's typical needs for i18n workflows.
The toolset covers key creation, retrieval, listing, and updates, but there are notable gaps: it lacks a delete_key tool for removing keys and a set_translation tool for updating translations individually (only available via create_key_with_translations). This forces agents into specific workflows and may cause failures when trying to modify translations without creating new keys.