Overview

What Glossa is, its concepts and every way to drive it.

Glossa stores every translatable string your apps ship, translates it with Claude, and lets people and agents review and improve the result. It reads the files you already have and writes them back in the same format.

Concepts

  • Workspace: your team. Holds projects, the glossary, rules, API keys and the review queue.
  • Project: one app or repo, with a source locale and target locales. Files belong to a project.
  • Key: a string as an app reads it, such as home.title in locales/en.json.
  • Unit: a deduplicated source string. Every key in the workspace with the same source text points at the same unit, which has one translation per locale. Fix it once and every key is fixed.
  • Op: a single action with a name and an input schema, such as push_file or resolve_task. The dashboard, REST API, MCP server and CLI all call the same ops.
  • Task: a decision in the review queue: a merge to confirm, a translation to check, an audit finding to apply.
  • Glossary and rules: terms that are fixed or never translated, and standing instructions per language. Both go into every translation prompt.

Ways to use it

Everything in the dashboard is available programmatically. Pick the surface that fits; they behave identically.

  • REST: POST https://glossa-meterapp.vercel.app/api/v1/{op} with a JSON body.
  • MCP: https://glossa-meterapp.vercel.app/api/mcp, one tool per op, for Claude Code, Codex, Cursor and other clients.
  • CLI: npx @meterapp/glossa, for terminals and CI.
List every op (no key needed)
curl https://glossa-meterapp.vercel.app/api/v1

Guides