MCP Filesystem

Created By
isaacphia year ago
Model Context Protocol (MCP) server with a resource for each file in a workspace
Overview

what is MCP Filesystem?

MCP Filesystem is a Model Context Protocol (MCP) server that exposes resources for each file in a working directory and sends change notifications.

how to use MCP Filesystem?

To use MCP Filesystem, install Go, fetch the server, and configure your client to access the MCP resources by specifying the workspace path in the client configuration.

key features of MCP Filesystem?

  • Creates one MCP resource for each file in your workspace
  • Respects .gitignore rules
  • Detects file changes, additions, and deletions
  • Identifies file types and handles various text encodings

use cases of MCP Filesystem?

  1. Managing file resources in a development environment
  2. Monitoring changes in a project directory
  3. Integrating with clients that support MCP features for file access

FAQ from MCP Filesystem?

  • What programming language is MCP Filesystem written in?

MCP Filesystem is written in Go.

  • Is there support for additional ignore patterns beyond .gitignore?

Currently, only .gitignore is supported, but future updates may include more options.

  • How can I report issues or provide feedback?

You can submit issues on the project's GitHub repository with as many details as possible.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
isaacphi
Star
0
Language
Go
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