In-depth architectural comparison of the Everything File Search and Obsideo MCP 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
Everything File Search
File Systems · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Obsideo MCP
File Systems · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Everything File Search if you need specialized File Systems tools running via a local process. Choose Obsideo MCP 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 Everything File Search 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).
Search for files and folders instantly using voidtools Everything.
Leverages Everything's real-time NTFS index for sub-millisecond search
across all local and mapped drives. Supports wildcards, regex, size/date
filters, extension filters, and path restrictions.
everything_search_by_type
Search for files by type category.
Categories: audio, video, image, document, code, archive, executable,
font, 3d, data. Each maps to a curated list of file extensions.
everything_find_recent
Find files modified within a recent time period.
Ideal for discovering what changed in a project, tracking recent
downloads, finding today's log files, etc. Sorted newest-first.
everything_file_details
Get detailed metadata and optional content preview for specific files.
Returns: full path, size, dates, type, permissions, hidden status.
For directories: item count, subdirectories, file listing.
For text files with preview_lines > 0: first N lines of content.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Everything File Search is categorized under File Systems and uses a local stdio subprocess. In contrast, Obsideo MCP belongs to File Systems using local stdio subprocess. Select Everything File Search when you need capabilities focused on file systems and Obsideo MCP when you require tools for file systems.
Get count and size statistics for files matching a query.
Fast way to understand the scope of a query without listing every file.
Optionally breaks down by extension for a high-level overview.
Obsideo MCP Tools (13)
trial
Create an instant no-email account (100 MB, ~7 days, proof-of-work, no human needed). Usually unnecessary: storage tools auto-create one on first use
signup_start
Email a 6-digit code (12 GB free tier; real inboxes only, refusals are labeled). With a trial configured this **claims it in place**: same account, keys and data, quota rises
signup_verify
Complete signup or the claim. A new account generates the signing keypair locally and stores credentials; a claim changes nothing but the quota
put
Store a file or inline content, encrypted client-side by default (`encrypt: false` opts out). Auto-creates a trial account if none is configured
get
Retrieve an object (auto-decrypts with the local key)
ls
List objects, optionally by prefix
rm
Delete an object
verify
Prove the network still holds an object, without downloading it
usage
Storage used vs quota, plus the plan line
backup_keys
Copy credentials, signing key, encryption key and upload commitments to a destination you give it (a .tar.gz path or a folder). No default: without a destination it refuses. Obsideo has no copy of the key
plan
Free tier or paid blocks, status, period end, any offer waiting for the human
upgrade
Stripe checkout link for N x 200 GB blocks. Charges nothing; the human pays on Stripe's page. Never changes an existing plan