Filesystem MCP Server (@shtse8/filesystem-mcp)

Created By
shtse8a year ago
Node.js Model Context Protocol (MCP) server providing secure, relative filesystem access for AI agents like Cline/Claude.
Overview

What is Filesystem MCP?

Filesystem MCP is a Node.js server that provides secure and relative filesystem access for AI agents like Cline and Claude, utilizing the Model Context Protocol (MCP).

How to use Filesystem MCP?

To use Filesystem MCP, you can deploy it via Docker, npx, or build it locally. For Docker, ensure your project directory is mounted to the container's /app directory.

Key features of Filesystem MCP?

  • Secure by Design: Operations are confined to the project root directory.
  • Comprehensive Toolset: Includes file listing, content manipulation, search and replace, directory management, deletion, and permissions management.
  • Modern Tech: Built with TypeScript and Node.js.
  • Input Validation: Uses Zod schemas for reliable argument validation.
  • Containerized: Available as a Docker image for easy deployment.

Use cases of Filesystem MCP?

  1. Empowering AI agents with controlled access to project files.
  2. Facilitating secure file operations in AI-driven applications.
  3. Managing project files efficiently within a defined directory structure.

FAQ from Filesystem MCP?

  • Can Filesystem MCP be used with any AI agent?

Yes! It is designed to work with AI agents like Cline and Claude.

  • Is there a Docker image available for Filesystem MCP?

Yes! It is available on Docker Hub for easy deployment.

  • How do I ensure security while using Filesystem MCP?

All operations are confined to the project root directory, preventing unauthorized access.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shtse8
Star
3
Language
TypeScript
License
MIT license

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
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.

a day ago