Aktar

io.github.getaktarv0.4.0Updated Oct 5, 2026

Upload files to your own S3, Cloudflare R2 or B2 bucket through the Aktar app and get links.

Overview

AI-generated overview

Lets an assistant upload files to your own S3, Cloudflare R2 or Backblaze B2 bucket through the Aktar desktop app and return shareable links.

What it does
Runs a local MCP server (aktar mcp) that uploads files through the Aktar app and returns the resulting link, Markdown and HTML. Tools include upload_file, upload_clipboard, replace_file, search_uploads, list_destinations, list_bucket, create_temporary_link, get_thumbnail, list_watched_folders, get_status and, only when enabled, delete_upload. Destinations, storage keys, path templates and link settings come from the Aktar app, so the CLI needs no extra configuration.
When to use it
Useful when an assistant should publish screenshots, reports, builds or other files to storage you control and hand back a link, or when it needs to look up past uploads, browse a bucket or create a temporary link. It fits workflows where files already go through the Aktar desktop app.
Requirements
Node.js 18 or later, plus the Aktar desktop app for Mac 0.4.0 or later or Aktar for Windows, running with local connections enabled. Connect first with aktar login using the token from Aktar's Settings > Integrations; the token is stored in the CLI config file or can be supplied via the AKTAR_TOKEN environment variable (and AKTAR_PORT if the port was changed). Desktop only.
Before you install
Uploading publishes a file, so review what the agent sends. delete_upload is only offered with --allow-delete; --root limits uploads to given folders and --read-only restricts the server to tools that change nothing. The token from Aktar is a credential; it is saved to the CLI config file or passed as AKTAR_TOKEN. Storage keys stay in the Aktar app.

Installation

In SourceWeft

  1. Open Aktar in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Aktar]

Aktar CLI

Upload files to your own S3, Cloudflare R2 or Backblaze B2 bucket from the terminal, and get the link.

[npm version] [CI] [MIT license]

[aktar upload in a terminal: links, Markdown and JSON output]

The aktar command talks to the Aktar app on your Mac or Windows PC, so it uses the destinations, keys, path templates and link settings you already set up there. Your storage keys never leave the app.

bash
$ aktar upload screenshot.pnghttps://files.example.com/2026/09/7f3c2a91.png

Install

bash
npm install -g @getaktar/cli# orbrew install getaktar/tap/aktar-cli

Or run it without installing: npx @getaktar/cli upload file.png.

Requires Node.js 18 or later and Aktar for Mac 0.4.0 or later, or Aktar for Windows.

Connect to Aktar

  1. In Aktar, open Settings > Integrations and turn on Allow local connections.
  2. Copy the token shown there.
  3. Run:
bash
aktar login

and paste the token when asked. It's checked against Aktar and saved to ~/.config/aktar/cli.json (%APPDATA%\aktar\cli.json on Windows), readable only by you. You can also pipe it in (pbpaste | aktar login) or set AKTAR_TOKEN (and AKTAR_PORT if you changed the port) instead.

Usage

bash
aktar upload report.pdf                     # prints the linkaktar upload *.png -f markdown              # one Markdown image per fileaktar upload build.zip -d Builds            # pick a destination by name or IDaktar upload notes.txt --folder docs/2026   # keep the name, upload into a folderaktar upload IMG_4021.jpg --name cover      # upload as cover.jpgaktar upload log.txt --expires 7            # delete after 7 daysaktar upload --clipboard                    # the file or image on the clipboardaktar upload demo.mp4 --qr                  # the link and a QR code to open it on your phoneaktar upload photo.jpg --json               # full details as JSON
aktar status                                # which Aktar and destination you're connected toaktar destinations                          # list destinations (* marks the selected one)aktar history invoice -n 5                  # search recent uploadsaktar replace 0B6C2F8E-3D1A-4C55-9E2B-7A41D0C3E9F1 v2.png  # new file, same linkaktar replace docs/guide.pdf guide.pdf -d Docs  # replace a key in a destination's bucketaktar qr https://example.com                # a QR code of any link or textaktar qr 0B6C2F8E-3D1A-4C55-9E2B-7A41D0C3E9F1  # a QR code of an upload in history

Without -d, files go to the destination selected in Aktar's menu bar. Uploads show up in Aktar's history like any other.

--format chooses what's printed: url (default), markdown, html, or custom (your template from Aktar). --expires takes 1, 7, 14 or 30 days and needs Aktar's auto-delete rules on that destination; without it, files are kept.

--name uploads a single file under another name: it's what {filename} and {ext} in the destination's path template become, and what Aktar's history shows. If the name has no extension, the file's own is added (--name cover uploads IMG_4021.jpg as cover.jpg); if it has one, it's used as given. With --folder, it's the name inside the folder.

If the same file (same contents, destination and expiry) is already in the bucket, Aktar doesn't upload it again and gives you the existing link. aktar prints the link as usual and notes it on stderr (aktar: photo.jpg: already uploaded, reused the existing link), so scripts reading stdout still get one link per file. This needs Aktar for Mac 0.10.0 or Windows 0.3.0.

QR codes

aktar upload --qr prints a QR code under each link, so you can open it on your phone. The QR code is always of the link itself, whatever --format prints. It's drawn black on white in the terminal, whatever its theme; when the output isn't a terminal, or NO_COLOR is set, it's drawn without colors (light modules as blocks), which phone cameras read on a light or dark background. --qr can't be combined with --json.

aktar qr <text> shows the QR code of any link or text; quote text with spaces. Given an upload ID from aktar history --json, it shows that upload's link and its QR code. --png <file> saves the QR code as a PNG instead:

bash
aktar qr https://files.example.com/2026/09/7f3c2a91.png --png link.png

What Aktar does for you

The app does the work per destination, so the CLI needs nothing extra for it:

  • Converting images to WebP or AVIF, if the destination is set to
  • {md5} and {sha256} in path templates, to name files by their contents
  • Big files: past 5 GB, Aktar uploads in parts and resumes after a dropped connection. aktar streams the file to the app, so its size doesn't matter

The link aktar prints is the one for the file as stored, after any conversion.

JSON output

aktar upload --json prints an array with one entry per uploaded file:

json
[  {    "id": "0B6C…",    "filename": "photo.jpg",    "objectKey": "2026/09/7f3c2a91.jpg",    "url": "https://files.example.com/2026/09/7f3c2a91.jpg",    "destinationId": "5D1A…",    "destinationName": "Screenshots",    "mimeType": "image/jpeg",    "size": 482113,    "createdAt": "2026-09-30T12:00:00Z",    "expiresAt": null,    "formats": { "url": "…", "markdown": "…", "html": "…", "custom": "…" },    "reused": false  }]

reused is true when nothing was uploaded because the file was already there; older versions of Aktar leave it out.

Exit codes

CodeMeaning
0Everything worked
1At least one upload or request failed (the others still went through)
2Bad arguments, or a file that doesn't exist (nothing was uploaded)
3Not logged in, Aktar isn't running, its local API is off, or the token is wrong

AI agents (MCP and skill)

MCP server

aktar mcp runs a Model Context Protocol server, so Claude, Cursor, VS Code, Codex and other agents can upload through Aktar, find past uploads and make links. Connect Aktar first (aktar login), then add it to your agent:

bash
claude mcp add aktar -- aktar mcp            # Claude Codecodex mcp add aktar -- aktar mcp             # Codex

For Claude Desktop, Cursor, VS Code and others that take a JSON config:

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

Without a global install, use "command": "npx", "args": ["-y", "@getaktar/cli", "mcp"].

ToolWhat it does
upload_fileUpload a file (destination, name, folder, expiry optional) and return its link, Markdown and HTML
upload_clipboardUpload what's on the clipboard
replace_fileWrite a new file over an upload, keeping its link (Mac 0.14.0 / Windows 0.7.0)
search_uploadsSearch upload history
list_destinationsDestinations and what file types each is used for
list_bucketBrowse a bucket's folders and files
create_temporary_linkA link that stops working after a while (presigned URL)
get_thumbnailA preview image of an upload (Mac 0.13.0 / Windows 0.6.0)
list_watched_foldersWatched folders and their status
get_statusCheck the connection
delete_uploadDelete an upload from its bucket (only with --allow-delete)

Uploading publishes a file, so keep an eye on what your agent sends. Your agent asks before calling a tool unless you allow it, and these options narrow what the server can do:

  • --root <folder>: only upload files from this folder (repeat for more). Paths are resolved, symlinks included, before they're checked.
  • --read-only: only the tools that change nothing (search, list, links, thumbnails).
  • --allow-delete: also offer delete_upload, which is left out by default.
bash
claude mcp add aktar -- aktar mcp --root ~/Projects --root ~/Desktop

The server speaks both the current per-request protocol (2026-07-28) and the earlier initialize versions (2024-11-05 to 2025-11-25).

Agent skill

Agents that use skills but not MCP can use the CLI directly. aktar skill prints a SKILL.md that teaches them how:

bash
mkdir -p ~/.claude/skills/aktar && aktar skill > ~/.claude/skills/aktar/SKILL.md

Typora

In Typora, open Settings > Image > Image Upload, choose Custom Command and enter:

aktar upload

Typora passes the image paths and reads one link per line. Click Test Uploader to check it.

Links

License

MIT

Source: README.md at commit 9ac1494

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.4.0LatestOct 5, 2026