Filesystem MCP Server SSE

Created By
ysthinka year ago
The SSE version of the MCP service is modified from the Filesystem MCP server
Overview

what is Filesystem MCP Server SSE?

Filesystem MCP Server SSE is a Node.js server that implements the Model Context Protocol (MCP) for filesystem operations, allowing users to perform various file and directory manipulations.

how to use Filesystem MCP Server SSE?

To use the server, you can either run it locally or in a Docker container. For local usage, install the necessary packages and run the server with the specified directory. For Docker, build the image and run it with the appropriate directory mounts.

key features of Filesystem MCP Server SSE?

  • Read and write files
  • Create, list, and delete directories
  • Move files and directories
  • Search for files
  • Retrieve file metadata

use cases of Filesystem MCP Server SSE?

  1. Managing files in a local or cloud environment.
  2. Automating file operations in applications.
  3. Providing a backend service for file management in web applications.

FAQ from Filesystem MCP Server SSE?

  • What operations can I perform with this server?

You can read, write, move, and delete files and directories, as well as search for files and get metadata.

  • Is there a limit to the directories I can access?

The server only allows operations within directories specified during setup.

  • What license is this project under?

The project is licensed under the MIT License, allowing free use, modification, and distribution.

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

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