MCP Server for FTP Access

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MCP Server for FTP Access?

MCP Server for FTP Access is a server that provides tools for interacting with FTP servers, allowing users to perform various file management tasks.

how to use MCP Server for FTP Access?

To use the MCP Server, install it via Smithery or build it from source, configure it with your FTP server details, and then use natural language commands to perform FTP operations.

key features of MCP Server for FTP Access?

  • List directory contents on the FTP server
  • Download files from the FTP server
  • Upload files to the FTP server
  • Create new directories on the FTP server
  • Delete files and directories on the FTP server

use cases of MCP Server for FTP Access?

  1. Managing files on an FTP server through natural language commands.
  2. Automating file uploads and downloads for data processing tasks.
  3. Organizing files by creating and deleting directories on the FTP server.

FAQ from MCP Server for FTP Access?

  • What are the prerequisites for using MCP Server?

You need Node.js 16 or higher and a compatible client like Claude for Desktop.

  • Can I use secure FTP with this server?

Yes, you can enable secure FTP (FTPS) by setting the appropriate environment variable.

  • How do I troubleshoot build issues on Windows?

Use the provided build script and ensure Node.js and npm are properly installed.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
-

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.

3 hours ago
Gpt Scrambler

2 days ago