cloud ShareWith
Help · AI access

Let an assistant work your files

ShareWith speaks the Model Context Protocol, so Claude — or any MCP-capable assistant — can list, read, move, copy, zip and delete your files directly. It connects as one specific user with a key you issue, and it can only touch what that key allows.

Connect Tools Limits & safety REST API For bots
Setup

Connect in three steps

1

Create a key

Open your files, switch the sidebar to API and choose New Key. Give it a name you will recognise. To confine the assistant to one folder, set that folder on the key — it will never see anything outside it. The key is shown once; copy it then.

2

Point your assistant at this server

The MCP endpoint is https://sharewith.xyz/mcp. It speaks JSON-RPC over HTTP POST and authenticates with the X-API-Key header.

Claude Code — one command:

claude mcp add --transport http sharewith https://sharewith.xyz/mcp \
  --header "X-API-Key: YOUR_KEY"

Claude Desktop — add this to your config file:

{
  "mcpServers": {
    "sharewith": {
      "type": "http",
      "url": "https://sharewith.xyz/mcp",
      "headers": { "X-API-Key": "YOUR_KEY" }
    }
  }
}

Clients that only accept a URL — some connectors (Google Gemini's "custom connected app", for example) give you one link field and no way to set a header. Put the key in the URL instead:

https://sharewith.xyz/mcp?key=YOUR_KEY

Leave any OAuth Client ID / secret fields blank — this server authenticates with an API key, not OAuth.

A key in a URL is easier to leak than a header — it ends up in browser history and web-server logs. Use a folder-scoped key for this, and revoke it if it gets out.
3

Ask for something

Try “list my files”, “put every invoice PDF into a folder called 2026 and zip it”, or “copy last night's backup from the FTP server into my own storage”. Mounted FTP, SFTP, Google Drive and shared server folders are all reachable, so the assistant can move files between machines in one step.

Capabilities

What the assistant can do

Thirteen tools, all going through the same engine as the web interface — so anything it does is exactly what you would get by clicking.

list_filesBrowse a folder, including mounted storage
read_fileRead a text file
write_fileCreate or overwrite a text file
create_folderMake a new folder
move_itemMove a file or folder, across mounts too
copy_itemCopy a file or folder, across mounts too
rename_itemRename in place
delete_itemDelete a file or a whole folder
get_file_infoSize, type and modified time
search_filesFind by name through subfolders
compress_itemsZip files and folders
extract_archiveUnpack a .zip
whoamiReport the account and folder limit
Safety

Limits worth knowing

The key is the boundary

A connection acts as exactly one user. A folder-scoped key cannot read, write or even list anything outside that folder, and .. in a path is rejected.

Deleting is permanent

There is no recycle bin. delete_item removes a folder and everything in it. Scope the key to a working folder if you want a safety net.

Read-only folders stay read-only

A folder an administrator shared as read-only refuses writes over MCP exactly as it does in the browser.

Revoke at any time

Delete the key in the API panel and the connection stops working immediately.

Treat a key like a password. Anyone holding it has the same file access the assistant does.
Alternative

Plain HTTP, if you prefer

Everything above is also a normal REST API, usable from a script, a cron job or any language.

# list the root
curl -H "X-API-Key: $KEY" "https://sharewith.xyz/api/v1/files?path="

# upload
curl -H "X-API-Key: $KEY" -F "file=@report.pdf" "https://sharewith.xyz/api/v1/files/upload?path=docs"
Full API reference arrow_forward
For bots

Machine-readable descriptions

If you are an agent reading this page, these describe the whole API without scraping HTML.

/llms.txtShort index of what this server is and where the docs are
/api/openapi.jsonOpenAPI 3.1 document for every endpoint
/api/docs.mdThe full reference as Markdown
/mcpMCP endpoint — POST JSON-RPC with an X-API-Key header