MCP server

1. Add the connector

   Connector URL

   https://mcp.freakingfast.io/mcp

   Claude has it in its connector directory: connect it there, and it follows you into the Claude apps. In ChatGPT, add the URL as a connector in settings. Any other client that takes a remote MCP server takes the same URL.

   In Claude Code, run this, then /mcp to sign in.

   Claude Code

   $ claude mcp add --transport http freakingfast https://mcp.freakingfast.io/mcp

2. Sign in and choose what it can do

   Your browser opens the drive, where you pick how much the app reaches, where, and for how long. Nothing is let in until you allow it.

3. Ask

   The tools a connection can't use aren't offered to it at all, so the model never reaches for something it would be refused.

Each level adds to the one before it. An app that asks for less can't be given more.

One folder#

Held to a folder, an app sees that folder and the ones inside it. Files it adds land there, and the tools that reach across the whole drive, like collections and image generation, are left out.

How long#

Choose when it stops working: never, a day, a week, a month or 3 months. Until then its access token lasts an hour at a time and renews itself.

A connection nobody uses for six months stops on its own. You can connect the same app more than once, say from two Claude accounts, and keep up to 10 connections to it. Past that, the one used least gives way.

Ask Claude to save an attachment or a file it made, and it lands in your drive. upload_file takes the file's name and size, Claude sends the bytes straight to storage, and complete_upload checks them and saves the file. It arrives private, in the connection's folder, or one you name.

It needs Organize access. Big files go in parts: Claude calls upload_file again with the same ticket for the next ones, or to pick an interrupted upload back up. A ticket lasts a day, and nothing is saved until complete_upload succeeds.

freaking-fast-mcp runs the drive's tools on your machine. Its upload_file uploads straight from your disk in one step, and it makes images. It needs Node 20 or later and an API token with full access.

$ claude mcp add freakingfast -e FREAKING_FAST_API_TOKEN=<token> -- npx -y freaking-fast-mcp

{
  "mcpServers": {
    "freakingfast": {
      "command": "npx",
      "args": ["-y", "freaking-fast-mcp"],
      "env": { "FREAKING_FAST_API_TOKEN": "<token>" }
    }
  }
}

• Uploads stream from disk, so a 2 TB file never has to fit in memory.
• Storage is checked before an upload starts. If a file won't fit, you find out right away.
• Uploading the same file again, with the same name, size and modified time, returns the one already stored.
• The token buys a session that lasts a day, renewed a minute before it runs out.

Share a folder or one file with someone else's AI, from the app or by asking your own: “share the Harbor folder with Sam's Claude”, or “share the interview with Ana's ChatGPT”. You get a link. Whoever you send it to adds it to their AI as a connector, with no account. For a folder, it can find, read and download what's in it and the folders inside it; for a file, it can read it, search inside it and download it. It changes nothing, and sees nothing else in your drive.

https://mcp.freakingfast.io/s/abs_…

In Claude it's a custom connector, in ChatGPT a connector in developer mode with no authentication, and in Claude Code claude mcp add --transport http harbor <link>. Opened in a browser, the link says the same. It stops on the day you chose, within a year, and you can stop it sooner from Agents, where you can also copy it again. A share stops when its folder or file is deleted, and a shared file in the trash opens nothing until it's back. What their AI does through it is listed on Agents with everything else.

Request links#

To get files back, send a file request's link. An AI connected to the drive, or to one of your shares, sends files to it with deliver_file and complete_delivery, the bytes going from its own environment straight to storage. An AI with no connection at all adds the request's own connector address, which the request page shows:

https://mcp.freakingfast.io/r/<request id>

Every tool, the least it needs, and whether an app held to one folder still has it. The connector has all of them but the two image tools, which only the server on your machine has. Its upload_file takes a name and size rather than a path.

Every app you connect, every folder you share, and every tool they call, is listed under Agents in the app, newest first, with what it touched. Disconnecting an app there stops it within a minute, and ends anything it had waiting. Stopping a share stops its link at once.

Undo takes back one thing an app did, or everything it did: files it trashed come back, and moves, tags, sharing and new uploads go back to how they were. Anything someone changed again since is left as it is. Through the connector, an app can only move files to the trash, so a delete can always be undone for 30 days.