BACH FileCommander
Let your agent search the repo, run local processes, manage sessions, OCR images, zip assets, and export PDFs through one 43-tool filesystem MCP server.
Overview
BACH FileCommander is a Build-phase MCP server that exposes 43 tools for local filesystem, process, session, search, OCR, ZIP, and PDF workflows for coding agents.
What is this MCP server?
- 43 MCP tools spanning filesystem operations, process management, sessions, search, OCR, ZIP archives, and PDF export
- stdio server via npx (`bach-filecommander-mcp`, v1.7.0) for laptop-first indie workflows
- Supports agent-driven document pipelines (OCR → PDF) without bespoke shell scripts per task
- Useful when scaffolding projects, bundling deliverables, or inspecting local logs during build and operate
- Broad local power user surface—review tool permissions before granting full filesystem access
- 43 documented MCP tools (filesystem, processes, sessions, search, OCR, ZIP, PDF)
- Server version 1.7.0; npm identifier `bach-filecommander-mcp`; stdio transport
Community signal: 3 GitHub stars.
What problem does it solve?
Coding agents struggle to reliably search disks, run processes, bundle files, or OCR documents without a unified, MCP-native local commander.
Who is it for?
Solo builders who want a single high-coverage local MCP integration for repo search, packaging, OCR, and light process control from Claude Code or Cursor.
Skip if: Builders who only need cloud SaaS APIs, remote-only sandboxes, or who cannot grant local filesystem and process permissions to an agent.
What do I get? / Deliverables
Once configured, your agent can perform structured local file and process operations, produce ZIPs and PDFs, and search the tree from one stdio MCP server.
- ZIP bundles and PDF exports generated through agent tool calls
- Search hits and OCR text usable in downstream build or docs steps
- Centralized local integration replacing scattered shell one-offs
Recommended MCP Servers
Journey fit
Build integrations is the primary shelf because FileCommander is how solo builders bridge agents to the local machine; Operate infra and docs export extend the same tools post-ship. integrations captures MCP wiring to OS-level capabilities—search, processes, archives, OCR—rather than a single app feature.
How it compares
43-tool local filesystem and process MCP server—not a remote cloud storage connector or a narrow single-file editor skill.
Common Questions / FAQ
Who is BACH FileCommander for?
It is for developer-agent users who need deep local machine access—files, processes, search, OCR, ZIP, and PDF—from MCP without writing a new script for each chore.
When should I use BACH FileCommander?
Use it during build and operate when agents must inspect repos, archive deliverables, OCR screenshots, export PDFs, or manage short-lived local processes.
How do I add BACH FileCommander to my agent?
Add the npm package `bach-filecommander-mcp` (v1.7.0) as a stdio MCP server with npx in your host config, restart the client, and scope allowed directories in your project rules.