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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago