MCP Server Filesystem Service

Created By
PimpMyNinesa year ago
MCP Filesystem Solution
Overview

what is MCP Server Filesystem Service?

MCP Server Filesystem Service is a highly scalable filesystem service designed for the MCP server, providing functionalities for file operations and security.

how to use MCP Server Filesystem Service?

To use the service, clone the repository, install dependencies, and run the service locally or in a Docker container.

key features of MCP Server Filesystem Service?

  • Validates and normalizes file paths
  • Supports reading, writing, and editing files with caching
  • Allows searching files by patterns
  • Creates directory trees and lists directories
  • Enforces security limits on file operations

use cases of MCP Server Filesystem Service?

  1. Managing file operations in a scalable server environment.
  2. Implementing secure file handling in applications.
  3. Facilitating efficient file searching and editing.

FAQ from MCP Server Filesystem Service?

  • Is the service easy to set up?

Yes! The service can be set up quickly by following the installation instructions in the repository.

  • Can I run it in a Docker container?

Yes! The service provides Docker support for both development and production environments.

  • What programming languages are used?

The service is built using TypeScript and Node.js.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
PimpMyNines
Star
-
Language
-
License
-
Category
file-systems

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)

2 days ago