Flamingo File Tools
Related Servers
Alternatives to Flamingo File Tools
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to browse and edit approved local workspace files, inspect and modify .xlsx spreadsheets, run terminal commands, and use previews and local approvals backed by path guards, backups, and audit logging.MIT
- FlicenseNot gradedqualityBmaintenanceEnables local publication cataloguing, persistent native DesignCraft editing sessions, page workspace operations, source linking via hoard:// references, preview rendering, and verified multipage RGB-raster PDF export through MCP tools.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients such as Claude, Cursor, and VS Code to compress, merge, split, rotate, protect, unlock, watermark, number pages, OCR, extract text, and convert PDFs and images locally without uploading files.73 npmMIT
- AlicenseBqualityBmaintenanceEnables local, offline batch image processing through MCP tools for resizing, converting, compressing, watermarking, and stripping EXIF metadata from files or folders.6MIT
- FlicenseNot gradedqualityCmaintenanceEnables cloud services with MCP support, such as Notion AI, to read, search, edit, create, and delete files within a single designated folder on your computer, and to run only allowed commands.4-
- AlicenseNot gradedqualityBmaintenanceEnables Gemini Spark to securely read, edit, and search a selected local workspace, execute shell commands, and integrate development tools via MCP with user approval safeguards.1MIT
TDQS
Scored across 6 tools
Each tool maps to a distinct product line and action: a meta-capabilities tool, MDB extraction, ad-ZIP optimization, PDF inspection, PDF stamping, and ONIX record preview. The only natural pair, patterncopy_inspect vs patterncopy_stamp, is explicitly differentiated as non-mutating preflight versus stamping. No two tools could plausibly be selected for the same task.
Four tools follow a clean <product>_<verb> pattern (access_extract, creativepack_optimize, patterncopy_inspect, patterncopy_stamp, shelfrelay_preview), all lowercase snake_case with unambiguous verbs. The lone 'capabilities' noun breaks the pattern but is a recognizable exception for a meta/describe tool.
Six tools is well-scoped: one meta tool plus one or two operations per supported product line, with nothing redundant. Each tool earns its place and the surface is easy to scan.
PatternCopy has a sensible inspect+stamp lifecycle, but ShelfRelay stops at preview with no apply/submit operation, and CreativePack offers optimize without an inspect/preflight counterpart. There is also no job-status, retry, or quota-check tool, leaving dead ends for multi-step or recovery workflows.