Let your AI agent share files from your own bucket

What you can ask

• Share a file from a session

  “Zip the build and give me a link I can send to QA.”

  The agent makes the file and uploads it. Without a destination named, Aktar picks one by file type (each destination's Use For), like a drop on the menu bar.

  Tools: upload_file

• Images for a README or an issue

  “Add the screenshot I just copied to the README.”

  It uploads the image, or what's on the clipboard, and writes the Markdown where it belongs. WebP conversion and location removal happen in Aktar, as the destination says.

  Tools: upload_file, upload_clipboard

• Update a file, keep its link

  “Replace the onboarding PDF I shared last week with this new version.”

  It finds the upload in history and writes the new file over it. Everyone who has the link sees the new version; nothing needs to be sent again.

  Tools: search_uploads, replace_file

• Find what you uploaded

  “What was the link to the invoice I uploaded on Monday?”

  It searches Aktar's history by name and date, and can look at thumbnails to tell screenshots, photos and documents apart.

  Tools: search_uploads, get_thumbnail

• A link that expires

  “Give me a 30-minute link to the contract in the Legal bucket.”

  A presigned link to any file in a bucket, for private buckets or sharing for a limited time. Nothing in the bucket changes.

  Tools: create_temporary_link

• Look around your buckets

  “What's in the releases folder of my Builds bucket?”

  It lists folders and files, including ones not uploaded with Aktar, and knows which destination is used for which file types.

  Tools: list_bucket, list_destinations

Set up in two steps

1. Install the aktar command and connect it to Aktar. In Aktar, open Settings > Integrations, turn on Allow local connections and copy the token, then paste it into aktar login.

   $ npm install -g @getaktar/cli
   $ aktar login

2. Add Aktar to your agent. The agent starts aktar mcp by itself when it needs it.

   Claude Code

   One command, for every project. Check with /mcp in Claude Code.

   $ claude mcp add --scope user aktar -- aktar mcp

   Codex

   One command; it goes into ~/.codex/config.toml.

   $ codex mcp add aktar -- aktar mcp

   Claude Desktop

   Open Settings > Developer > Edit Config, add this, and restart Claude Desktop.

   In claude_desktop_config.json

   {
     "mcpServers": {
       "aktar": { "command": "aktar", "args": ["mcp"] }
     }
   }

   Cursor

   Add this to the file, or to .cursor/mcp.json in one project.

   In ~/.cursor/mcp.json

   {
     "mcpServers": {
       "aktar": { "command": "aktar", "args": ["mcp"] }
     }
   }

   VS Code

   One command adds it to your VS Code profile. Copilot's agent mode then lists Aktar's tools.

   $ code --add-mcp '{"name":"aktar","command":"aktar","args":["mcp"]}'

   Windsurf

   Add this to the file, then refresh the MCP servers in Windsurf's settings.

   In ~/.codeium/windsurf/mcp_config.json

   {
     "mcpServers": {
       "aktar": { "command": "aktar", "args": ["mcp"] }
     }
   }

Tools your agent gets

You decide what it can touch

• Uploading is publishing

  The agent is told to upload only what you asked to share, and agents ask before calling a tool that uploads.

• Only from your folders

  --root limits uploads to the folders you name. Paths are resolved, symlinks included, so a link to ~/.ssh or a .env elsewhere is refused.

• Read-only, and no deleting

  --read-only leaves out every tool that writes. Deleting from a bucket isn't offered at all unless you add --allow-delete.

• Your keys stay in Aktar

  The server talks to Aktar on 127.0.0.1 with your token. The agent never sees your access keys, and nothing goes through a server of ours.

$ aktar mcp --root ~/Projects --root ~/Desktop
$ aktar mcp --read-only

Questions