Skip to main content
Glama
File Merger MCP Server

File Merger MCP Server

by exoticknight

Servidor MCP de fusión de archivos

Utilidad sencilla para combinar varios archivos en uno. Rápida, segura y fácil de usar.

Características

  • Simple : fusiona cualquier cantidad de archivos con un solo comando

  • Rápido : combina de manera eficiente archivos de cualquier tamaño

  • Seguro : solo accede a los directorios que usted permite

  • Detallado : informes de tamaño de archivos y resumen de combinación

Related MCP server: File Server MCP

API

Herramientas

  • archivos de fusión

    • Entradas:

      • inputPaths (string[]): Archivos a fusionar

      • outputPath (cadena): Ubicación del archivo de salida

    • Devoluciones:

      • Mensaje de éxito con detalles de la fusión

  • lista_de_directorios_permitidos

    • Enumera los directorios a los que puede acceder el servidor

Uso con Claude Desktop

Añade a tu claude_desktop_config.json :

{
  "mcpServers": {
    "file-merger": {
      "command": "npx",
      "args": [
        "-y",
        "@exoticknight/mcp-file-merger",
        "/path/to/allowed/dir"
      ]
    }
  }
}

Instalación

# Clone and install
git clone https://github.com/exoticknight/mcp-file-merger.git
cd mcp-file-merger
npm install
npm run build

Licencia

Licencia Apache 2.0

Available Tools

2 tools
list_allowed_directoriesA

Returns the list of directories that this server is allowed to access. Use this to understand which directories are available before trying to merge files.

Inputs: no named parameters.

merge_filesA

Merge multiple files into a single output file. Reads content from each input file in the order provided and writes it sequentially to the output file. Returns information about the merge operation including file sizes and total size. All specified paths must be within allowed directories if specified.

Inputs: inputPaths (required), outputPath (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: one lists accessible directories for context, while the other performs the core file merging operation. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the task.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun naming pattern (list_allowed_directories and merge_files), using clear verbs that describe their actions. The naming is predictable and readable throughout the set.

    Tool Count2/5

    With only two tools, the server feels under-scoped for a file merging domain. While the tools cover basic operations, there are likely missing functionalities such as file validation, conflict resolution, or format-specific merging that would enhance completeness. A count of 2 is too low for robust file handling.

    Completeness2/5

    The toolset is severely incomplete for file merging. It lacks essential operations like checking file compatibility, handling merge conflicts, supporting different merge strategies (e.g., concatenation vs. intelligent merging), or providing previews. This will likely cause agent failures when dealing with complex merging scenarios.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      D
      maintenance
      Enables accessing and managing files from configured folders with filtering and size limits, allowing listing, reading, and searching files via MCP tools and resources.
      3
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables managing files across multiple FTP servers through a single MCP interface, supporting upload, listing, deletion, and public URL generation.
      107 npm
      MIT