File MCP

Created By
mattlemmonea year ago
WIP MCP server for file management.
Overview

what is File MCP?

File MCP is a Model Context Protocol (MCP) server that provides file system operations through a standardized API, primarily aimed at prototyping and integrating error logs into MCP clients.

how to use File MCP?

To use File MCP, you can run the server using the command line interface (CLI) with the following commands:

  1. Build the project: npm run build
  2. Start the server: npm start
  3. For development, use: npm run dev
  4. For testing, use: npm run inspect

key features of File MCP?

  • Provides a standardized API for file system operations.
  • Tools for reading, writing, and listing files.
  • Ability to read the last N lines from a file.
  • Lists all tools registered in the server.

use cases of File MCP?

  1. Integrating file management capabilities into applications.
  2. Prototyping error logging systems for MCP clients.
  3. Developing tools that require file system interactions.

FAQ from File MCP?

  • What programming language is File MCP written in?

File MCP is written in TypeScript.

  • Is File MCP open source?

Yes, File MCP is available under the MIT license.

  • How can I contribute to File MCP?

You can contribute by submitting issues or pull requests on the GitHub repository.

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

35 minutes ago