Feature • Last updated: July 29, 2026

FTPie MCP Server - Your Storage, in Your AI Assistant

One MCP server for every storage you already use - Google Drive, Dropbox, OneDrive, Box, S3, SFTP and your NAS - with the file picker, viewer and transfer queue of a real Windows file manager behind it.

In development - targeted for September 2026

This page describes a feature we are building, not one you can download today. It is planned as part of FTPie Pro, alongside the command-line interface. Watch the release notes for the shipping announcement. Everything below is what it is being built to do - if that is useful to you, tell us, because it shapes what lands first.

MCP - the Model Context Protocol - is an open standard that lets an AI assistant call external tools. An MCP server publishes a set of actions the assistant can use on your behalf, and file storage was one of the first things people wired up: read this document, find that folder, put the result somewhere I can get to it.

Because it is an open standard rather than one vendor's integration, a single MCP server works across whichever AI clients and coding agents you use - and keeps working when you switch.

That part is well covered. There is an MCP server for Google Drive, one for Dropbox, one for S3, one for the local filesystem. What nobody covers is the situation most people are actually in: files spread across several of those at once, plus a company SFTP box and a NAS in the corner of the room.

One server instead of six

Single-provider MCP servers each need their own install, their own authorization, and their own entry in your client configuration. Three clouds means three of everything - and none of them can talk to each other, so "copy the signed contract from Dropbox to the archive on my NAS" is not a thing any of them can express.

FTPie already holds those connections. You set an account up once in the app, and the MCP server exposes all of them through one endpoint - the same accounts, the same credentials, the same engine the GUI uses. Cross-storage transfer is not a bolt-on here; moving a file from one provider to another is what the app is built around, so the assistant gets it for free.

What it will be able to do

  • Browse and search - list folders, read metadata, search by name, total up folder sizes, across any connected storage
  • Read a file - fetch a document so the assistant can actually work with its contents
  • Move things - upload, download, copy, move and rename, including directly between two different providers
  • Organize - create folders, delete with confirmation, tidy up a directory
  • Ask you - open FTPie's file picker so you choose the file, rather than the assistant guessing at paths

The part a headless server cannot do

Every other file MCP server runs invisibly. It has no window, so it cannot show you anything, cannot ask you anything, and cannot let you watch what it did. FTPie has a window - and that turns out to be the interesting half:

  • Pick a file in a real dialog. The assistant asks for a file; FTPie's browser opens; you choose it. No pasted paths, no guessing, no accidental wrong folder.
  • Documents open in FTPie. Ask it to show you a file and it appears in FTPie's own viewer or editor - not as a wall of text in the chat.
  • Transfers you can see. Anything it moves runs through the normal transfer queue, with progress, speed and a cancel button. Nothing happens invisibly in the background.
  • Review round-trips. "Open this contract, let me read it, then apply the changes we discussed and put it back" - open, wait for you, edit, re-upload, as one flow.

Your credentials never reach the model

Handing an AI assistant access to every cloud account you own deserves more care than a config file full of API keys. The design rule is simple: credentials stay in FTPie. Passwords, OAuth tokens and refresh tokens are never sent to the model or included in any tool result - the assistant works with opaque references to files instead. Destructive actions ask for confirmation, and because the work runs through the app, you see it happen. Local-only by design, like the rest of FTPie - see the security page.

Storage it will cover

Everything FTPie already connects to - if you can browse it in the app, the MCP server can reach it:

What you can do today

While this is in development: several providers publish their own MCP servers, and if you only need one storage, those are a reasonable place to start - Anthropic and Google both document connecting Google Drive, and there are community servers for Dropbox, S3 and the local filesystem. They cover one provider each, which is exactly the limitation this feature exists to remove.

If you want scriptable access to all your storage right now, that already exists and is not waiting on anything: the FTPie CLI drives the same connections from PowerShell, a batch file or CI, with structured exit codes and --json output. An AI assistant that can run shell commands can already use it - the MCP server is about doing that properly, with confirmations, a picker and a visible transfer queue.

Common questions

What is an MCP server?

MCP (Model Context Protocol) is an open standard that lets an AI assistant use external tools. An MCP server exposes a set of actions - here, browsing and moving files - that the assistant can call on your behalf, with your approval. It is supported by a growing number of AI clients and coding agents, so the same server works across whichever ones you use.

How is this different from the official Google Drive or Dropbox MCP servers?

Those cover one provider each, so using three clouds means running and authorizing three separate servers. FTPie exposes every storage you have already connected through a single server - and because it is a real file manager, it can also move files directly between them.

Does the AI get my passwords or cloud tokens?

No. Credentials stay inside FTPie on your machine. The assistant only ever receives opaque references to files, never account passwords, OAuth tokens or refresh tokens.

Can I see what it is doing?

Yes - that is the point of putting a GUI behind it. Transfers appear in FTPie's normal transfer queue with progress and cancel, and files it opens are shown in FTPie's own viewer.

When will it be available?

It is in development, targeted for September 2026 as part of FTPie Pro. Watch the release notes.

Related

Start Your 14-Day Free Trial

Download FTPie and start your free 14-day trial. Enjoy seamless FTP + cloud integration and keep using the free version afterward.

Download Free Trial
CASA Verified & VirusTotal Scanned
14-day trial · Free version included
Windows 10 & 11