list_allowed_directories
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.
LABSCO SUMMARY
One call for a job that otherwise costs a read and a write per file.
The contents never pass through the model, so the size of what you are merging never lands in the conversation — that is the difference between this and asking an agent to do the same thing with generic file tools. The allow-list is the thing to check first, since paths outside it are refused and the lookup tool is the only way to see where the boundary sits.
What it is
A two-tool file server: a merge that reads each input in the order given and writes it sequentially to an output path, and a lookup of the directories it may access.
What you get
- Multiple files joined into one output file, in the order the input paths were given
- Size information back from the merge — the individual file sizes and the total
- The list of directories the server is allowed to access, checkable before a merge is attempted
Requirements
Input and output paths that sit inside the allowed directories, which list_allowed_directories reports.
Setup effort
One command — npx -y @exoticknight/mcp-file-merger <YOUR_PATH_TO_ALLOWED_DIR>
USE CASES
01
Stitching a day of log files into one artefact
Check which directories are in scope, then merge the files in the order you listed them — the sizes come back with the result, and none of the content passes through the conversation.
02
Assembling a document from sections written separately
Order is the whole contract here: the inputs are concatenated exactly as listed, so the sequence of the paths is the sequence of the finished file.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
merge_files
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.
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected.
Requires
npx on PATH
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @exoticknight/mcp-file-merger <YOUR_PATH_TO_ALLOWED_DIR>MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"file-merger": {
"command": "npx",
"args": [
"-y",
"@exoticknight/mcp-file-merger",
"<YOUR_PATH_TO_ALLOWED_DIR>"
]
}
}
}<YOUR_PATH_TO_ALLOWED_DIR> is the directory holding the files to merge and the output. Add more directories as further arguments. Without one, the server only reaches the directory the client starts it in.
