Glossa

dev.getglossaPublished by getglossa.devOfficial publisherv0.1.2Updated Nov 5, 2026

AI-native translation management: push translation files, translate, review and audit strings.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Glossa is an AI-native translation management server that lets an assistant push translation files and translate, review and audit strings.

What you can do
  • Push translation files to a Glossa project
  • Translate strings with AI assistance
  • Review and audit existing translations
  • Run as a remote endpoint or as a local stdio process
When to use it
Use it when a project keeps localization files and you want an assistant to help push them, translate new strings, and review or audit existing translations without leaving the chat.
Requirements
Either the remote endpoint at getglossa.dev or the local npm package @meterapp/glossa over stdio. OAuth authentication is required; a Glossa API key can be supplied through the GLOSSA_API_KEY environment variable, though it is optional once the glossa login command has stored one.
Before you install
The server requires authentication and can push translation files and change strings in your Glossa project, so review writes before approving them. The API key is a secret; keep it out of shared configuration. Translation content is sent to Glossa's service.

Installation

In SourceWeft

  1. Open Glossa in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.getglossa%2Fglossa/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "glossa": {
      "type": "http",
      "url": "https://getglossa.dev/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v0.1.2LatestNov 5, 2026
  2. v0.1.1Nov 3, 2026
  3. v0.1.0Nov 3, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.