BetterMCPFileServer

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is BetterMCPFileServer?

BetterMCPFileServer is a reimagined Model Context Protocol (MCP) server designed for filesystem access, focusing on privacy-preserving path aliases and an optimized API for large language models (LLMs).

How to use BetterMCPFileServer?

To use BetterMCPFileServer, clone the repository, install the dependencies, and run the server with alias-directory pairs to access your files through privacy-preserving aliases.

Key features of BetterMCPFileServer?

  • Path Aliasing System: Protects privacy by hiding full system paths.
  • LLM-Optimized Interface: Simplified API with fewer functions while maintaining full capability.
  • Smarter Search: Unified tool for directory listings and complex file searches.
  • Privacy-First Design: Prevents exposure of usernames or system paths to AI models.

Use cases of BetterMCPFileServer?

  1. Securely accessing files with privacy-preserving aliases.
  2. Simplifying interactions between LLMs and filesystem operations.
  3. Enhancing privacy in AI applications that require filesystem access.

FAQ from BetterMCPFileServer?

  • Can BetterMCPFileServer be used with any programming language?

Yes! It can be integrated with any language that can make HTTP requests.

  • Is BetterMCPFileServer free to use?

Yes! It is open-source and free to use under the MIT License.

  • How does the path aliasing system work?

It maps user-defined aliases to actual paths, keeping sensitive information hidden.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago