filesystem-mcp-server

Created By
johntawfika year ago
Overview

what is filesystem-mcp-server?

filesystem-mcp-server is a server application designed to manage and interact with file systems in a multi-cloud environment.

how to use filesystem-mcp-server?

To use filesystem-mcp-server, clone the repository from GitHub, configure the server settings, and run the server command to start managing your file systems.

key features of filesystem-mcp-server?

  • Multi-cloud file system management
  • Easy configuration and setup
  • Support for various file operations

use cases of filesystem-mcp-server?

  1. Managing files across different cloud platforms.
  2. Automating file backups and synchronization.
  3. Providing a unified interface for file operations in a multi-cloud setup.

FAQ from filesystem-mcp-server?

  • What cloud platforms does filesystem-mcp-server support?

filesystem-mcp-server supports major cloud platforms like AWS, Google Cloud, and Azure.

  • Is there a user guide available?

Yes! A detailed user guide is available in the repository's README file.

  • Can I contribute to the project?

Absolutely! Contributions are welcome, and you can find guidelines in the repository.

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