verbatra

Name: verbatra
Author: verbatra

by verbatraversion 0.3.0i★ –iRuns on your computer

Registry nameio.github.verbatra/verbatra

Install

Overview

Description from the maker (original English)

Translation status, glossary, and editing tools for a verbatra i18n project, over stdio.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: ANTHROPIC_API_KEY, OPENAI_API_KEY, GEMINI_API_KEY, DEEPL_API_KEY, GOOGLE_TRANSLATE_API_KEY, OPENCODE_API_KEY, OPENAI_COMPATIBLE_API_KEY, LIBRETRANSLATE_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: VERBATRA_MCP_ALLOW_SPEND, VERBATRA_MCP_REDACT_VALUES, ANTHROPIC_API_KEY, OPENAI_API_KEY, GEMINI_API_KEY, DEEPL_API_KEY, GOOGLE_TRANSLATE_API_KEY, OPENCODE_API_KEY, OPENAI_COMPATIBLE_API_KEY, LIBRETRANSLATE_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "verbatra": {
      "command": "npx",
      "args": [
        "-y",
        "@verbatra/mcp"
      ],
      "env": {
        "VERBATRA_MCP_ALLOW_SPEND": "your-value",
        "VERBATRA_MCP_REDACT_VALUES": "your-value",
        "ANTHROPIC_API_KEY": "your-value",
        "OPENAI_API_KEY": "your-value",
        "GEMINI_API_KEY": "your-value",
        "DEEPL_API_KEY": "your-value",
        "GOOGLE_TRANSLATE_API_KEY": "your-value",
        "OPENCODE_API_KEY": "your-value",
        "OPENAI_COMPATIBLE_API_KEY": "your-value",
        "LIBRETRANSLATE_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add verbatra --env VERBATRA_MCP_ALLOW_SPEND=your-value --env VERBATRA_MCP_REDACT_VALUES=your-value --env ANTHROPIC_API_KEY=your-value --env OPENAI_API_KEY=your-value --env GEMINI_API_KEY=your-value --env DEEPL_API_KEY=your-value --env GOOGLE_TRANSLATE_API_KEY=your-value --env OPENCODE_API_KEY=your-value --env OPENAI_COMPATIBLE_API_KEY=your-value --env LIBRETRANSLATE_API_KEY=your-value -- npx -y @verbatra/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "verbatra": {
      "command": "npx",
      "args": [
        "-y",
        "@verbatra/mcp"
      ],
      "env": {
        "VERBATRA_MCP_ALLOW_SPEND": "your-value",
        "VERBATRA_MCP_REDACT_VALUES": "your-value",
        "ANTHROPIC_API_KEY": "your-value",
        "OPENAI_API_KEY": "your-value",
        "GEMINI_API_KEY": "your-value",
        "DEEPL_API_KEY": "your-value",
        "GOOGLE_TRANSLATE_API_KEY": "your-value",
        "OPENCODE_API_KEY": "your-value",
        "OPENAI_COMPATIBLE_API_KEY": "your-value",
        "LIBRETRANSLATE_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "verbatra": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@verbatra/mcp"
      ],
      "env": {
        "VERBATRA_MCP_ALLOW_SPEND": "your-value",
        "VERBATRA_MCP_REDACT_VALUES": "your-value",
        "ANTHROPIC_API_KEY": "your-value",
        "OPENAI_API_KEY": "your-value",
        "GEMINI_API_KEY": "your-value",
        "DEEPL_API_KEY": "your-value",
        "GOOGLE_TRANSLATE_API_KEY": "your-value",
        "OPENCODE_API_KEY": "your-value",
        "OPENAI_COMPATIBLE_API_KEY": "your-value",
        "LIBRETRANSLATE_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

VERBATRA_MCP_ALLOW_SPEND env
Set to true to advertise the two provider-calling tools, the same as --allow-spend.
VERBATRA_MCP_REDACT_VALUES env
Set to true to replace translation values in every tool result with a marker, the same as --redact-values.
ANTHROPIC_API_KEY secret env
API key for the anthropic provider, read only by the provider-calling tools.
OPENAI_API_KEY secret env
API key for the openai provider, read only by the provider-calling tools.
GEMINI_API_KEY secret env
API key for the gemini provider, read only by the provider-calling tools.
DEEPL_API_KEY secret env
API key for the deepl provider, read only by the provider-calling tools.
GOOGLE_TRANSLATE_API_KEY secret env
API key for the google-translate provider, read only by the provider-calling tools.
OPENCODE_API_KEY secret env
API key for the opencode provider, read only by the provider-calling tools.
OPENAI_COMPATIBLE_API_KEY secret env
API key for the openai-compatible provider, read only by the provider-calling tools.
LIBRETRANSLATE_API_KEY secret env
API key for the libretranslate provider, needed only when the server runs with --api-keys, read only by the provider-calling tools.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account verbatra, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32476 servers in this category
Published to the registry more recently than 77% of the other 32476 servers in this category
Basic checks equal to or better than 100% of the other 32476 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is verbatra safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: ANTHROPIC_API_KEY, OPENAI_API_KEY, GEMINI_API_KEY, DEEPL_API_KEY, GOOGLE_TRANSLATE_API_KEY, OPENCODE_API_KEY, OPENAI_COMPATIBLE_API_KEY, LIBRETRANSLATE_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 10 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, zanadir

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

zanadir

by MustacheCase

Find what a repository's CI is missing, and which security checks cannot fail the build.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@verbatra/mcp

Stdio MCP server exposing verbatra's translation status, glossary, and editing capabilities as tools for any MCP client, without a browser.

Documentation | Connect a client | Changelog | Issues

Description

@verbatra/mcp starts a Model Context Protocol server over stdio, the standard local-process transport an MCP client uses to launch and talk to a tool server. It gives a terminal-hosted or headless agent the same translation-status, glossary, and editing capabilities Verbatra Studio exposes in the browser, without a browser, a port, or a served single-page app. It is a thin, SDK-backed surface over @verbatra/sdk, the same way @verbatra/cli is.

Installation

Most MCP clients spawn the server for you and need no local install at all: point the client at npx -y @verbatra/mcp and npx fetches it on demand. To pin it in your project instead:

npm install --save-dev @verbatra/mcp

Needs Node.js ^22.18.0 || >=24. The server is also reachable through verbatra mcp once both @verbatra/cli and @verbatra/mcp are installed.

Configuring an MCP client

Point your client at the verbatra-mcp binary, which the @verbatra/mcp package provides (the example runs it through npx). The shape below is the one most clients use; for an editor or desktop client, put it in that client's MCP server configuration file.

"mcpServers": { "verbatra": { "command": "npx", "args": ["-y", "@verbatra/mcp", "--cwd", "/path/to/your/project"], "env": {} } } }

In Claude Code, npx @verbatra/cli init --agent (or claude mcp add --transport stdio --scope project verbatra -- npx -y @verbatra/mcp) writes an equivalent entry to a committed .mcp.json. The verbatra plugin bundles the agent skills with its own copy of this server, so use it instead of the .mcp.json entry, never both: together they register the server twice. VS Code (GitHub Copilot's agent mode) reads .vscode/mcp.json, whose top-level key is servers rather than mcpServers. The exact file, key, and working-directory handling for every client is in Connect an MCP client.

That configuration is read-only plus local editing: no provider is called and no API key is needed. Add --allow-spend to args, and the environment variable your configured provider reads its key from, once you also want the two provider-calling tools. --config loads a specific config file instead of searching for one, and VERBATRA_MCP_ALLOW_SPEND is the environment equivalent of the flag, which the flag always wins over.

Tools

Every tool, listed in the order the server advertises them.

Tool	What it does
`project.snapshot`	Read the resolved project configuration: whether a usable config is loaded (`configured`), locales, format, path pattern, provider id, where the config came from, whether a glossary is configured
`project.doctor`	Check the project setup (config, format, provider, API key variable by name, network policy, source file) and get a `fix` for every failed check, with or without a usable config
`status.check`	Per target locale, how many keys are missing, stale, or up to date, and whether the locale is in sync
`status.diff`	Per target locale, the exact keys the next translate run would add, re-translate, or orphan
`glossary.get`	Every glossary term with its translation for all locales, per-locale translations, forbidden renderings, case sensitivity, note and part of speech, the terms kept untranslated, the glossary version and where it comes from; with `locale`, also the terms that locale is held to
`glossary.write`	Change one glossary term (a translation for all locales or one `locale`, `forbidden` renderings, `note`, `partOfSpeech`, `caseSensitive`, or `doNotTranslate`) and return the glossary afterward
`lock.state`	The lock file's version and its per-locale key counts, or `exists: false` before the first run
`history.list`	Recent git commits that touched a locale file, with hash, author name (never the email), date, subject and touched paths
`key.integrity`	One key's placeholder, inline markup, and ICU drift against the lock-file baseline, per locale
`locale.integrity`	Every translation that fails the placeholder, markup or ICU checks right now, per target locale
`key.value`	One key's current source text, its source file description, and, if translated, its current text in one target locale with who wrote it
`key.context`	What `key.value` returns plus the glossary terms that apply, the key's `maxLength`, and a check of an optional `draft`
`locale.values`	Source and target text of many keys, filtered by `keys` or a `query`, in pages of up to 1,000 entries
`translation.editEntry`	Write a manual translation for one key in one locale, accepted only if it passes the integrity gate
`translation.estimate`	Estimate what `translation.translatePending` would send and cost, optionally for a subset of locales, without calling a provider
`translation.retranslateEntry`	Ask the configured provider for a fresh translation of one key in one locale
`translation.translatePending`	Translate every missing or stale key across the configured target locales, or a named subset, in one run, within an optional `maxTokens` ceiling
`review.queue`	Every machine-written translation nobody has approved yet, read from the committed files, with the last run's flags
`report.provenance`	Per locale, how many values fall into each provenance bucket; with `includeEntries`, the keys, paged
`review.approve`	Record, on the user's instruction, that a named person approves one key's current translation
`review.reject`	Record, on the user's instruction, that a named person rejects one key's current translation, removing it so it gets replaced
`usage.summary`	Token usage and budget status left behind by the last run

Security and spend

Spend is opt-in. translation.retranslateEntry and translation.translatePending are the two tools that call a provider. They are advertised only when the server is started with --allow-spend or VERBATRA_MCP_ALLOW_SPEND; without either, a client never sees them and calling one by name fails as an unknown tool. A config with provider: { id: "none" } never lists them, even with --allow-spend.
Values can stay home. --redact-values (or VERBATRA_MCP_REDACT_VALUES) replaces every source text, translation, description, and glossary term in a result with a marker such as [redacted length=12 hash=3f9a0c1d2e4b5a6c], and leaves out reviewer and author names. Key names, counts, statuses, and integrity verdicts stay. review.approve and review.reject then take only the marker's hash as expectedHash, locale.values refuses query, and key.context refuses draft. This keeps values out of results; it does not stop an agent that probes on purpose, and what a provider receives does not change.
Secrets are scrubbed. Every result and log line passes through a redaction pass first, so a value shaped like a provider API key, or the exact value of a configured provider variable, becomes [REDACTED] before it reaches the client or stderr.
Stdout is protocol only. Nothing but MCP messages is written to stdout; every log and diagnostic line goes to stderr.
Config changes need no restart. The server starts without a usable config (project.snapshot reports configured: false, project.doctor says what to fix) and reloads the config and its glossary file before each call. --allow-spend is fixed at startup, and a config change never widens it.

Every tool's input, and every closed-shape tool output, is a JSON Schema derived from the same zod schema the server validates the call against. See the verbatra mcp docs for the full tool reference, the exit-code contract, and worked examples.

Documentation

Related packages

@verbatra/sdk: the engine this server is a thin surface over.
@verbatra/cli: the verbatra command, including verbatra mcp.
@verbatra/studio: the same capabilities in a browser dashboard.

Contributing

See CONTRIBUTING.md.

License

MIT (c) Mario Kreitz

verbatra

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

zanadir

README from the maker

Description

Installation

Configuring an MCP client

Tools

Security and spend

Documentation

Related packages

Contributing

License