Skip to main content
Glama
exoticknight

File Merger MCP Server

by exoticknight
README.md
[![MseeP.ai Security Assessment Badge](https://mseep.net/pr/exoticknight-mcp-file-merger-badge.png)](https://mseep.ai/app/exoticknight-mcp-file-merger)

[![Trust Score](https://archestra.ai/mcp-catalog/api/badge/quality/exoticknight/mcp-file-merger)](https://archestra.ai/mcp-catalog/exoticknight__mcp-file-merger)

# File Merger MCP Server

Simple utility to combine multiple files into one. Fast, secure, and easy to use.

<a href="https://glama.ai/mcp/servers/@exoticknight/mcp-file-merger">
  <img width="380" height="200" src="https://glama.ai/mcp/servers/@exoticknight/mcp-file-merger/badge" alt="File Merger Server MCP server" />
</a>

## Features

- **Simple** - Merge any number of files with a single command
- **Fast** - Efficiently combines files of any size
- **Secure** - Only accesses directories you allow
- **Detailed** - Reports file sizes and merge summary

## API

### Tools

- **merge_files**
  - Inputs:
    - `inputPaths` (string[]): Files to merge
    - `outputPath` (string): Output file location
  - Returns:
    - Success message with merge details

- **list_allowed_directories**
  - Lists directories the server can access

## Usage with Claude Desktop

Add to your `claude_desktop_config.json`:

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

## Installation

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

## License

Apache License 2.0

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 issues