Filesystem MCP Server

Created By
jayessdeeseaa year ago
Overview

what is Filesystem MCP Server?

The Filesystem MCP Server is a Model Context Protocol (MCP) server that provides resources for accessing file metadata and content, allowing clients to retrieve information about files and directories, as well as read the content of files.

how to use Filesystem MCP Server?

To use the Filesystem MCP Server, you need to build it using Maven and run the generated JAR file. You can access file metadata and content through specific endpoints.

key features of Filesystem MCP Server?

  • Get metadata for files and directories (name, path, size, timestamps, permissions, etc.)
  • Read the content of text and binary files
  • Automatic MIME type detection based on file extension
  • Comprehensive logging

use cases of Filesystem MCP Server?

  1. Accessing file metadata for file management applications.
  2. Reading content from files for data processing tasks.
  3. Integrating with other applications that require file access capabilities.

FAQ from Filesystem MCP Server?

  • What are the prerequisites to run the server?

You need Java 17 or higher and Maven installed.

  • How do I build the project?

You can build the project by running mvn clean package in the terminal.

  • What license is the project under?

The project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jayessdeesea
Star
0
Language
Java
License
MIT license
Category
file-systems
Tags

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