Oxidize Python vs Filestash — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Oxidize Python vs Filestash
In-depth architectural comparison of the Oxidize Python and Filestash MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Oxidize Python
File Systems · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Filestash
File Systems · Local stdio
Quality: 40/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Oxidize Python if you need specialized File Systems tools running via a local process. Choose Filestash if your workspace requires File Systems integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Oxidize Python when:
You need dedicated capabilities in the File Systems domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: OXIDIZE_WORKSPACE, OXIDIZE_ALLOWED_PATHS, OXIDIZE_MAX_FILE_SIZE_MB, OXIDIZE_MAX_PAGES, OXIDIZE_MAX_OUTPUT_BYTES, OXIDIZE_MAX_SESSIONS, OXIDIZE_MAX_SESSION_BYTES, OXIDIZE_SESSION_TIMEOUT.
Primary tools included: Read PDF metadata including page count and encryption status, Extract text from all or specific pages, Create, save, and manipulate PDF sessions with encryption support.
Rust-powered PDF toolkit: create, read, and analyze PDFs; extract text and entities for RAG; convert to Markdown; split, merge, rotate, and reorder pages; add content, annotations, and form fields; and encrypt documents. Ships in the oxidize-pdf PyPI package — run locally with uvx oxidize-mcp.
Oxidize Python is categorized under File Systems and uses a local stdio subprocess. In contrast, Filestash belongs to File Systems using local stdio subprocess. Select Oxidize Python when you need capabilities focused on file systems and Filestash when you require tools for file systems.
Primary tools included: Plugin-driven architecture for extensibility, Support for over 20 storage protocols including SFTP, FTP, SMB, S3, WebDAV, Git, and cloud providers, Universal access via web client, APIs, and protocol gateways.