extract_data

Programmatically extract embedded i18n translations or configuration data from source code into structured JSON files, ensuring clean separation of content and code for streamlined workflows.

Instructions

Extract data content (e.g. i18n translations) from source code to a JSON file. IMPORTANT: When encountering files with data such as i18n content embedded in code, use this tool directly instead of reading the file content first. This tool will programmatically extract all translations into a structured JSON file, preserving nested objects, arrays, template variables, and formatting. This helps keep translations as configuration and prevents filling up the AI context window with translation content. By default, the source file will be replaced with "MIGRATED TO <target absolute path>" and a warning message after successful extraction, making it easy to track where the data was moved to. This behaviour can be disabled by setting the DISABLE_SOURCE_REPLACEMENT environment variable to 'true'. The warning message can be customized by setting the WARNING_MESSAGE environment variable.

Input Schema

Name	Required	Description	Default
`sourcePath`	Yes	Path to the source file containing data inside code
`targetPath`	Yes	Path where the resulting JSON file should be written

Input Schema (JSON Schema)

{
  "properties": {
    "sourcePath": {
      "description": "Path to the source file containing data inside code",
      "type": "string"
    },
    "targetPath": {
      "description": "Path where the resulting JSON file should be written",
      "type": "string"
    }
  },
  "required": [
    "sourcePath",
    "targetPath"
  ],
  "type": "object"
}

mcp-data-extractor

extract_data

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from mcp-data-extractor

Related Tools