Filesystem MCP Server

Created By
sergiobayonaa year ago
Ruby server implementing Model Context Protocol (MCP) for filesystem operations using the
Overview

what is Filesystem MCP Server?

Filesystem MCP Server is a Ruby server that implements the Model Context Protocol (MCP) for performing various filesystem operations.

how to use Filesystem MCP Server?

To use the server, configure it with the appropriate paths in the claude_desktop_config.json file, specifying the script location and allowed directories.

key features of Filesystem MCP Server?

  • 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?

  1. Managing files and directories in a structured manner.
  2. Automating file operations in applications.
  3. Integrating with other systems that require filesystem access.

FAQ from Filesystem MCP Server?

  • What programming language is used for the server?

The server is implemented in Ruby.

  • Can I use this server for any directory?

No, the server only allows operations within directories specified in the configuration.

  • How do I configure the server?

You need to edit the claude_desktop_config.json file to include the server's script path and allowed directories.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sergiobayona
Star
0
Language
Ruby
License
-
Category
file-systems

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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.

5 hours ago