mcpField
J
JSON Translations MCP Server

JSON Translations MCP Server

Local
github.com/schmklsDeveloper Tools0Updated 78w ago

About JSON Translations MCP Server

JSON Translations MCP Server provides tools for reading and updating translations in nested JSON files. It is designed for managing language-specific strings through dot-notation keys, while preserving file structure and formatting.

Key features

  1. 01Read translations by dot-notation key
  2. 02Update nested translation values
  3. 03Work with multiple language files
  4. 04Preserve JSON structure and formatting
  5. 05Configure an optional default path

Use cases

  1. 01Look up a localized string by key
  2. 02Edit nested translations across language files

MCP support

Exposes translation retrieval and update tools to MCP clients, with an optional default translations path.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

JSON Translations MCP Server

A Model Context Protocol (MCP) server for updating and retrieving translations in JSON files.

Overview

This MCP server provides two tools: update-translation and get-translation. These tools allow you to update and retrieve translations in JSON files for different languages. It's designed to work with nested translation structures where keys are separated by dots.

Features

  • Update translations in JSON files using a dot-notation path
  • Retrieve translations from JSON files using a dot-notation path
  • Support for multiple language files
  • Preserves JSON structure and formatting
  • Handles nested translation keys
  • Graceful error handling
  • Optional default translations path

Tool: update-translation

Parameters
  • translationId - The translation ID using dot notation (e.g., "common.buttons.save")
  • language - The language code for the translation file (e.g., "sv", "en", ...)
  • path - (Optional) Path to the folder containing translation files. If not provided, the default path set during server initialization will be used.
  • translation - The new translation value to be inserted
Example
{
  "translationId": "common.buttons.save",
  "language": "en",
  "translation": "Save"
}

Tool: get-translation

Parameters
  • translationId - The translation ID using dot notation (e.g., "homepage.welcome.message")
  • language - The language code for the translation file (e.g., "sv", "en", ...)
  • path - (Optional) Path to the folder containing translation files. If not provided, the default path set during server initialization will be used.
Example
{
  "translationId": "homepage.welcome.message",
  "language": "en"
}

Setup and Usage

Prerequisites
  • Node.js or Bun
Installation
From npm
npm install -g json-translations-mcp-server
From source
  1. Clone the repository
  2. Install dependencies:
bun install
# or
npm install
Build
bun run build
# or
npm run build
Run
# If installed from npm globally
json-translations-mcp-server --path /path/to/translations
# or
json-translations-mcp-server -p /path/to/translations

# If running from source
bun start --path /path/to/translations
# or
npm run start -- --path /path/to/translations

Development

Testing
bun test

Project Structure

json-translations-mcp-server/
├── src/
│   ├── main.ts                         # Server entry point
│   └── tools/
│       ├── updateTranslation/
│       │   ├── index.ts                # Tool implementation
│       │   └── schema.ts               # Tool schema
│       └── getTranslation/
│           ├── index.ts                # Tool implementation
│           └── schema.ts               # Tool schema
├── tests/                              # Test files
├── biome.json                          # Linting configuration
├── tsconfig.json                       # TypeScript configuration
└── package.json                        # Project dependencies

Adding to Claude Desktop

To add the MCP server to Claude Desktop:

If installed from npm
{
  "mcpServers": {
    "json-translations-mcp-server": {
      "command": "json-translations-mcp-server",
      "args": ["--path", "/path/to/translations"]
    }
  }
}
If using from source
  1. Build the project:

    bun run build
    
  2. Add to your Claude Desktop config with default path:

    {
      "mcpServers": {
        "json-translations-mcp-server": {
          "command": "bun",
          "args": [
            "/path/to/your/project/dist/main.js",
            "--path",
            "/path/to/translations"
          ]
        }
      }
    }
    
  3. Or without default path (will require path in each tool call):

    {
      "mcpServers": {
        "json-translations-mcp-server": {
          "command": "bun",
          "args": ["/path/to/your/project/dist/main.js"]
        }
      }
    }
    

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.