# StringLane (npm · @stringlane/cli)

Check, translate and fix app localization files — ARB, iOS strings, Android XML, i18next JSON.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- npm · `@stringlane/cli`: 63/100 (this document), [markdown](https://verifymcp.io/servers/thebedcoder-stringlane/stringlane-cli.md), [page](https://verifymcp.io/servers/thebedcoder-stringlane/stringlane-cli)

## Channel facts

- Registry: `npm`
- Package: `@stringlane/cli`
- Version: `0.4.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-26.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license.
  - Actively maintained (last published 0 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2848 tokens (~284/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the StringLane MCP server?

StringLane runs locally as an npm package, launched with npx -y @stringlane/cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add thebedcoder-stringlane -- npx -y @stringlane/cli
```

### Cursor

```json
{
  "mcpServers": {
    "thebedcoder-stringlane": {
      "command": "npx",
      "args": [
        "-y",
        "@stringlane/cli"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "thebedcoder-stringlane": {
      "command": "npx",
      "args": [
        "-y",
        "@stringlane/cli"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add thebedcoder-stringlane -- npx -y @stringlane/cli
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "thebedcoder-stringlane": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@stringlane/cli"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add thebedcoder-stringlane --command npx --arg -y --arg @stringlane/cli
```

### Hermes

```yaml
mcp_servers:
  thebedcoder-stringlane:
    command: "npx"
    args: ["-y", "@stringlane/cli"]
```

### Netclaw

```json
{
  "McpServers": {
    "thebedcoder-stringlane": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@stringlane/cli"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add thebedcoder-stringlane -t stdio -c npx -a -y @stringlane/cli
```

### Other

```json
{
  "mcpServers": {
    "thebedcoder-stringlane": {
      "command": "npx",
      "args": [
        "-y",
        "@stringlane/cli"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 63)

First indexed and scored.

## MCP tools (10)

### `inspect_project` (~51 tokens)

Inspect the project’s localization state

Report this project’s locales, missing and stale strings, and every validation finding, as the stringlane engine sees them. Reads only; writes nothing. Takes no arguments — the project is fixed when the server starts.

### `read_translations` (~206 tokens)

Read existing translations

Look up what this project already says — one key across locales, or keys matching a search, decoded exactly as the stringlane engine reads them. Use this instead of opening a locale file: four of the five supported formats escape, prefix or nest their values, so the bytes on disk are not the string. Reads only; writes nothing. Takes no file paths — the project is fixed when the server starts.

Input parameters:

- `cursor` (string): nextCursor from a previous result. Opaque — pass it back, do not parse it.
- `key` (string): An exact key, as prepare_translation_plan spells it. Omit to list.
- `limit` (integer): Maximum translations (not keys) per page. Default 200, maximum 2000.
- `locales` (array): Locale codes to read. Omit for every locale, base included.
- `query` (string): Case-insensitive substring matched against KEYS, not values. Cannot be used with key.

### `read_key_usage` (~181 tokens)

Find where a key is used, or which keys are unused

Report where a translation key is called in this project’s source code, or list the keys nothing appears to call. Use this instead of grepping: it knows the call shapes of each supported framework, matches the spelling the runtime actually uses rather than the merged key, and refuses rather than guessing when it cannot read your code. "Not referenced" is what the scanner SAW, not a verdict — read the caveat before deleting anything. Reads only; writes nothing.

Input parameters:

- `cursor` (string): nextCursor from a previous result. Opaque — pass it back, do not parse it.
- `key` (string): A merged key, exactly as prepare_translation_plan spells it. Omit to list unused keys.
- `limit` (integer): Maximum unused keys per page. Default 200, maximum 2000. Ignored when key is given.

### `prepare_translation_plan` (~158 tokens)

Prepare a translation plan

List exactly the strings that need translating, each with its base value, metadata, placeholders and plural categories, plus the project’s translation context. Returns a planId to pass to validate_translations and apply_translations. Reads only; writes nothing. Takes no file paths — the project is fixed when the server starts.

Input parameters:

- `after` (integer): Number of items already received. Use with planId to continue.
- `limit` (integer): Items per page. Default 100, maximum 2000.
- `planId` (string): To fetch a further page of a plan you already have. Omit to make a new plan.
- `targets` (array): Locale codes to plan for. Omit for every locale except the base.

### `validate_translations` (~111 tokens)

Validate candidate translations

Check candidate translations against a plan — placeholders, ICU structure, plural categories, length constraints — and report every problem. Writes nothing, anywhere. A clean result means these candidates would be accepted, but it is not permission to write: apply_translations re-runs every check itself and also verifies the project has not changed since the plan was made.

Input parameters:

- `candidates` (array, required): One entry per plan item you are answering.
- `planId` (string, required): The planId from prepare_translation_plan, this session.

### `apply_translations` (~111 tokens)

Apply translations to the project files

Write validated translations into the project’s locale files. It re-runs every check validate_translations runs, and additionally refuses if the project changed since the plan was made — a clean validate earlier grants nothing. Either every proposed change lands or none does. Your host asks the user before this runs, and git is where they review what it wrote.

Input parameters:

- `candidates` (array, required): One entry per plan item you are answering.
- `planId` (string, required): The planId from prepare_translation_plan, this session.

### `describe_keys` (~109 tokens)

Write key descriptions

Store a description for one or more keys, so every future translation is made against context instead of a guess. WRITES to your project. A description is stored where this format keeps one: the ARB @key block, an iOS or Android comment, or .stringlane/metadata.yaml. Describing a key that is already translated marks that translation stale, so describe before you translate.

Input parameters:

- `descriptions` (array, required): One entry per key you are describing. An unknown key refuses the whole set.

### `add_locale` (~183 tokens)

Add a locale to the project

Create the file for a locale this project does not have yet, in the right place and the right format. WRITES to your project. Use this when prepare_translation_plan comes back empty because there is nothing to translate INTO. Never write a locale file yourself: the path, the format and the plural categories differ per project, and a hand-made file skips every check. This creates the FILE. It does not make the app OFFER the language — that lives in the app's own source (a supportedLocales list, Info.plist, a locale config, supportedLngs, a language picker) and each of those is optional per project, so check rather than assume. Do not report a locale as ready before you have.

Input parameters:

- `locale` (string, required): BCP 47 code — "uk", "fr-CA", "zh-Hans". Not the base locale.

### `set_project_context` (~156 tokens)

Set the project translation context

Store what this product IS, how it should sound, per-locale notes, and words that must never be translated. WRITES to stringlane.yaml. These shape every future translation in every locale, so they are worth getting right once. Omit a field to leave it alone; pass an empty value to remove it.

Input parameters:

- `brandingGuidelines` (string): Voice, tone, address form, and anything never to translate.
- `guardedWords` (array): Words that must survive translation unchanged. No empty entries.
- `localeContext` (object): Locale code to notes. A locale the project does not have is refused.
- `productContext` (string): What the product is and who uses it. Empty string removes it.

### `add_key` (~249 tokens)

Add new keys to the project

Add new translation keys and their source strings to the base locale. Use this when you have just written code referencing keys the project does not have yet. WRITES to your project. Send them ALL IN ONE CALL — one call is one atomic write, so a component never ends up half-keyed. Include a description for each key: you are holding the context nobody recovers later, and a key without one is reported by the very next prepare_translation_plan as still needing it. Never add a key by editing the locale file: key names are not equally legal across formats, a description belongs wherever THIS format keeps one, and a hand edit skips both checks. It writes the BASE locale only; every other locale then reports the keys as missing, so translate them with prepare_translation_plan as usual. Adding the key is HALF the job: until those locales have it, the string ships in the base language to everyone else, so do not report the work as done when this returns — localesToTranslate on the result is how many are waiting. A key that already exists refuses the whole set rather than overwriting.

Input parameters:

- `keys` (array, required): One entry per key. An invalid key refuses the whole set.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/thebedcoder-stringlane/stringlane-cli#diagnostics

## Score history

- 2026-09-26: 63
- 2026-09-25: 63

## Common questions

### What is the StringLane MCP server?

StringLane is an MCP server listed in the public MCP registry as io.github.thebedcoder/stringlane. Check, translate and fix app localization files, ARB, iOS strings, Android XML, i18next JSON. This page covers its npm package (@stringlane/cli).

### Is the StringLane MCP server safe to use?

StringLane scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the StringLane MCP server expose?

StringLane exposes 10 tools: inspect_project, read_translations, read_key_usage, prepare_translation_plan, validate_translations, and 5 more. Their descriptions and schemas cost roughly 1,515 tokens of context every time the server is loaded.

### Is the StringLane MCP server still maintained?

StringLane is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- npm package: https://www.npmjs.com/package/@stringlane/cli
- Socket report: https://socket.dev/npm/package/@stringlane/cli
- Website: https://stringlane.app/docs/cli/mcp-setup
- Changelog RSS feed: https://verifymcp.io/servers/thebedcoder-stringlane/stringlane-cli.xml
- Changelog JSON feed: https://verifymcp.io/servers/thebedcoder-stringlane/stringlane-cli.json
- HTML version of this page: https://verifymcp.io/servers/thebedcoder-stringlane/stringlane-cli