.

Created By
expsh13a year ago
Overview

what is Filesystem MCP Server?

Filesystem MCP Server is a project designed to provide a fast and efficient server for managing file systems using Bun, a modern JavaScript runtime.

how to use Filesystem MCP Server?

To use the Filesystem MCP Server, first install the necessary dependencies by running bun install, and then start the server with bun run index.ts.

key features of Filesystem MCP Server?

  • Built with Bun for high performance
  • Easy installation and setup
  • Supports TypeScript for better development experience

use cases of Filesystem MCP Server?

  1. Managing file systems in web applications
  2. Serving static files efficiently
  3. Developing applications that require file manipulation and storage

FAQ from Filesystem MCP Server?

  • What is Bun?

Bun is a fast all-in-one JavaScript runtime that allows for quick development and execution of JavaScript applications.

  • Is the Filesystem MCP Server free to use?

Yes! The Filesystem MCP Server is open-source and free to use under the MIT license.

  • What programming language is used in this project?

The project is developed using TypeScript.

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

a day ago
Payai X402 Tools

6 hours ago