Filesystem Context Mcp Server

Created By
j0hanz6 months ago
Read-only MCP server for secure filesystem exploration, searching, and analysis
Overview

what is Filesystem Context Mcp Server?

Filesystem Context Mcp Server is a read-only MCP server designed for secure filesystem exploration, searching, and analysis.

how to use Filesystem Context Mcp Server?

To use the server, install it via npm with the command npx -y @j0hanz/filesystem-context-mcp@latest and utilize its various tools for directory and file operations.

key features of Filesystem Context Mcp Server?

  • 🔒 Security-first: Ensures read-only operations with path validation.
  • 🚫 Symlink protection: Prevents directory escape attacks.
  • Batch operations: Allows efficient parallel file reading.
  • 📊 Rich metadata: Provides detailed information on file types, sizes, permissions, and MIME types.
  • 🔍 Powerful search: Supports glob patterns and regex content search.

use cases of Filesystem Context Mcp Server?

  1. Securely exploring filesystem structures without risk of modification.
  2. Conducting detailed file analysis and gathering metadata.
  3. Performing complex searches within files using regex patterns.

FAQ from Filesystem Context Mcp Server?

  • Is the Filesystem Context Mcp Server secure?

Yes! It is designed with security in mind, allowing only read-only operations.

  • Can I modify files using this server?

No, it is strictly read-only to ensure filesystem integrity.

  • How do I install the server?

You can install it using the command: npx -y @j0hanz/filesystem-context-mcp@latest.

Server Config

{
  "mcpServers": {
    "filesystem-context": {
      "command": "npx",
      "args": [
        "-y",
        "@j0hanz/filesystem-context-mcp"
      ]
    }
  }
}
Project Info
Created At
6 months ago
Updated At
6 months ago
Author Name
j0hanz
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)

a day ago
Crevio

2 days ago