Glossa

MCP and agent plugins

Connect Claude Code, Codex, Cursor and any MCP client to Glossa.

The MCP server is at https://glossa-meterapp.vercel.app/api/mcp over streamable HTTP. It exposes one tool per op, with the op's description and input schema, and marks read-only tools so clients can approve them automatically. Its instructions tell the agent how the workspace fits together.

Authentication

  • API key: send Authorization: Bearer gls_…. Create keys in the dashboard under Settings → API keys, or with the create_api_key op. Keys act as an admin of their workspace.
  • OAuth: clients that support MCP authorization can connect without a key. The server answers 401 with a pointer to its protected resource metadata; the client signs you in through the browser and uses the workspace you belong to.

Plugin (recommended)

The Glossa plugin bundles the MCP connection with skills for pushing files, working the review queue, running audits and teaching formats. It signs in with OAuth, so no key is needed.

Claude Code

/plugin marketplace add MeterApp/glossa-plugins/plugin install glossa@meterapp

Then open /mcp, select the Glossa server and authenticate in your browser.

Codex

codex plugin marketplace add MeterApp/glossa-pluginscodex plugin add glossa@meterapp

Cursor

git clone https://github.com/MeterApp/glossa-plugins.gitmkdir -p ~/.cursor/plugins/localln -s "$(pwd)/glossa-plugins" ~/.cursor/plugins/local/glossa

Skills only, any agent

npx skills add MeterApp/glossa-plugins

Manual setup

Claude Code

claude mcp add --transport http glossa https://glossa-meterapp.vercel.app/api/mcp \  --header "Authorization: Bearer gls_…"

Leave out the header to sign in with OAuth instead: claude mcp add --transport http glossa https://glossa-meterapp.vercel.app/api/mcp.

Codex

~/.codex/config.toml
# ~/.codex/config.toml
[mcp_servers.glossa]
url = "https://glossa-meterapp.vercel.app/api/mcp"
bearer_token_env_var = "GLOSSA_API_KEY"

Export GLOSSA_API_KEY in the environment Codex runs in.

Cursor

.cursor/mcp.json
{  "mcpServers": {    "glossa": {      "url": "https://glossa-meterapp.vercel.app/api/mcp",      "headers": {        "Authorization": "Bearer gls_…"      }    }  }}

Other clients

Any client that supports streamable HTTP works with the URL and header. For stdio-only hosts, use the CLI bridge:

{  "mcpServers": {    "glossa": {      "command": "npx",      "args": [        "-y",        "@meterapp/glossa",        "mcp"      ],      "env": {        "GLOSSA_API_KEY": "gls_…"      }    }  }}

Things to ask

  • “Push locales/en.json to Glossa and pull every locale.”
  • “Work through the review queue. Split merges whose context differs.”
  • “How is our German? Run an audit and apply the fixes you agree with.”
  • “Find every string that mentions checkout and make sure the glossary covers our product names.”

Agents should read agents.md for rules such as never changing placeholders. The same tools are available over REST and the CLI (npx @meterapp/glossa).