← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionCLIO ParquetMCP server for Apache Parquet filesObsidian Web MCPSecure remote access to your Obsidian vault over HTTPS with OAuth 2.0 authentication.
FMRS55 / 100 · C68 / 100 · C
Reliability8 / 209 / 20
Security and permissions12 / 2016 / 20
Maintenance13 / 2014 / 20
Documentation10 / 2017 / 20
Setup experience12 / 2012 / 20
Best for
  • Data exploration in scientific computing and HPC environments.
  • AI agents that need to quickly summarize Parquet files.
  • Workflows integrated with the CLIO Kit ecosystem, where other servers provide complementary functions.
  • Users who want secure remote access to their Obsidian vault from any device.
  • Integrating Claude.ai (web) or mobile with Obsidian.
  • Those needing concurrent writes with Obsidian Sync without file conflicts.
Not for
  • Full-fledged data analysis with complex transformations (e.g., group by aggregates), which might require dedicated tools.
  • Handling extremely large files where the entire data cannot fit into memory for operations like reading all rows.
  • Users who only need local stdio MCP access without remote capabilities.
  • Those unwilling to set up an OAuth password or use a Cloudflare Tunnel.
  • Users with extremely high security requirements who distrust network exposure (though encrypted).
Required permissions
  • Read access to Parquet files in the local file system as provided by the user.
  • Perform file I/O to read file metadata and contents.
  • Read and write files in the directory specified by VAULT_PATH.
  • Perform file operations (move, delete with soft delete to .trash).
  • Create daily notes, write binary files.
  • Maintain an in-memory frontmatter index, potentially modifying index files.
  • Access the network (for Cloudflare Tunnel, heartbeat URLs).
Risks and side effects
  • Potential exposure of sensitive data if inputs include unexpected file paths.
  • Resource-intensive operations on large files or complex queries could lead to excessive memory or CPU consumption.
  • Credential leakage: exposed OAuth password or MCP token could allow unauthorized access.
  • Path traversal mitigation is not infallible; keep updated.
  • Extension system is not sandboxed; loading untrusted extensions could be risky.
  • Audit log is best-effort and not tamper-evident; records may be dropped at runtime.
  • Misconfiguration may cause the server to fail to start or expose vulnerabilities.
Supported clientsClaude Desktop, Claude Code, Cursor, VS CodeClaude Desktop, Claude Mobile, Claude Web
Tools420