RawbackRawbackRawback
HomePricing
Log inSign up

Download options

Desktop ClientiOS AppCLICore SDKMCP
RawbackRawbackRawback

The agentic AI platform for photographers — keep every RAW, understand every frame, and work from the app, CLI, or Core SDK.

Photographs deserve better than a database

Product

  • Pricing
  • Desktop Client
  • iOS App
  • CLI
  • Core SDK
  • MCP Connector
  • FTP Access

Resources

  • Camera Setup Guide
  • CLI Guide
  • SDK Guide
  • Changelog
  • GitHub
  • Contact Support

Legal

  • Privacy Policy
  • Terms of Service

© 2026 Rawback. All rights reserved.

v0.0.93Powered byEvonia.ai
Back to the MCP connector

Rawback MCP documentation

What the connector can do

Every action your assistant can take on your library once the connector is added — and the permission each one needs.

On this page

  1. 01Before you start
  2. 02Photos and tags
  3. 03Albums and shares
  4. 04Album stories
  5. 05Videos
  6. 06Account and usage
  7. 07ChatGPT compatibility
  8. 08Permissions
  9. 09Limits and safety

Before you start

Every action on this page runs through the Rawback MCP server at https://api.rawback.app/v3/mcp. If you have not added the connector yet, set it up first — the assistant discovers the sign-in flow on its own once you point it at that URL.

Three things apply to everything below.

The connector is part of a paid plan. You can add it on the free plan, but every action refuses with an upgrade message until the account has a membership.

Access covers your own library only. There is no action that reaches another person's photos, albums or stories, whatever the assistant is asked.

Secret albums are invisible to the connector. They are unlocked by typing a private keyword in the web app, and nothing here lists them, opens them by ID, or reads the stories written for them.

Reconnect to use videos and album stories

Video and album-story actions need permissions that did not exist when older connections were approved. If you added the connector before those actions shipped, the assistant will say a permission was not granted — remove the connector and add it again to grant them.

Photos and tags

ActionWhat it doesPermission
search_imagesSearch by free text, camera, lens, city, country, date range, rating, aperture or focal length. Also filters archived photos and sorts by rating.Photos · read
get_imageOne photo in full: description, AI title and description, tags, exposure settings, location, album membership and image URLs.Photos · read
list_peopleThe people in your face library.Photos · read
list_tagsYour tags, optionally filtered by keyword.Photos · read
update_imageChange a photo's title, description or rotation.Photos · write
archive_imageMove a photo to the archive. Reversible.Photos · write
unarchive_imageRestore an archived photo.Photos · write
delete_imagePermanently delete a photo and its stored files.Photos · write
create_tagCreate a tag, with an optional colour.Photos · write
add_tags_to_imageApply one or more tags to a photo.Photos · write
remove_tags_from_imageRemove tags from a photo.Photos · write

Ask for these in your own words — "find the shots from Lisbon last spring rated four or better", "tag everything from the harbour trip", "archive the out-of-focus ones".

Archive rather than delete

archive_image is reversible; delete_image is not, and the tool description tells the assistant to prefer archiving unless you asked for deletion outright.

Albums and shares

ActionWhat it doesPermission
search_albumsList or search your albums by name.Albums · read
get_albumOne album with a page of the photos inside it.Albums · read
list_sharesThe public share links you have created, with their URLs and expiry.Albums · read
create_albumCreate an album with a name, description and visibility.Albums · write
update_albumRename an album, change its description or change who can see it.Albums · write
add_images_to_albumAdd photos to an album.Albums · write
remove_images_from_albumRemove photos from an album.Albums · write
delete_albumDelete an album. The photos in it are not deleted.Albums · write

Album stories

A story is an album's written companion: Markdown plus an ordered selection of that album's photos. An album has at most one story, which is why there is no separate "create" action — upsert_article writes the album's story whether or not one already exists.

ActionWhat it doesPermission
list_articlesYour album stories, most recently edited first. Includes drafts.Stories · read
get_articleOne story in full — its Markdown, its status, and the album photos it embeds. Identify it by story ID or by album ID.Stories · read
get_article_public_linkThe story's public URL, or the reason it does not have one yet.Stories · read
upsert_articleWrite or edit an album's story: title, Markdown body, and which album photos it embeds.Stories · write
publish_articlePublish the story to the album's audience, optionally putting it on the open web in the same step.Stories · write
unpublish_articleReturn the story to draft. Always withdraws it from the open web too.Stories · write
set_article_web_publicTurn the open-web link on or off without changing whether the story is published.Stories · write
delete_articlePermanently delete the story and any pictures uploaded into it. The album is untouched.Stories · write

Published is not the same as public

Two separate switches, and it is worth knowing which is which:

  • Published means everyone who can already reach the album can read the story. Sharing the album shares the story.
  • On the open web means anyone at all can read it at /articles/…, search engines included. It is off by default, and publishing alone never turns it on.

A draft cannot go on the open web — publish it first. Returning a story to draft always pulls it back off.

Ask before it goes public

set_article_web_public and publish_article with the web option are the only actions here that expose anything outside your account. Make sure the assistant is acting on a request you actually made.

Embedded pictures

Story Markdown embeds pictures as stable tokens rather than URLs: rawback://image/{id} for a photo drawn from the album, and rawback://article-image/{id} for a picture uploaded to the story itself. An assistant editing a story should leave those tokens intact — Rawback resolves them to real images when the page is rendered.

Pictures can only be uploaded into a story from the web editor. The connector can rearrange and embed what is already there, not add new files.

Videos

ActionWhat it doesPermission
list_videosYour videos, newest first. Only uploads that finished appear here.Videos · read
get_videoOne video's details: duration, dimensions, codecs, playback and poster-frame URLs, and whether a transcript exists. Also finds uploads that are still in progress or failed.Videos · read
get_video_transcriptThe speech-to-text transcript, as plain text or as SRT subtitle cues.Videos · read
update_videoChange a video's title or description.Videos · write
delete_videoPermanently delete a video with its poster frame, audio and transcript.Videos · write

The transcript is the reason this group is worth connecting: it lets an assistant answer questions about what was actually said in a recording, quote a passage, or find the clip where something came up.

Long transcripts are shortened so a single video cannot consume the whole conversation — ask for more if the assistant reports the text was cut short. A video only has a transcript once its audio has been uploaded and the background job has run, and transcription is a per-deployment setting; when there is none, the action explains why rather than failing.

Videos are uploaded from the apps, not the connector

Uploading a video needs the file itself and measurements taken from it before the upload starts, which is work the desktop app, the CLI and iOS do on your machine. There is no upload action here — use one of those, then come back and the connector will see the result.

Account, recaps and usage

ActionWhat it doesPermission
get_profileYour name, email address and plan.Account · read
list_equipmentThe cameras and lenses detected in your library.Account · read
list_notificationsYour notifications, optionally unread only.Account · read
list_dreamsYour daily AI photo recaps.Photos · read
get_dreamOne recap in full.Photos · read
mark_notifications_readMark one notification, or all of them, as read.Account · write
get_usageStorage used, AI credit balance and face-recognition quota.Usage · read

ChatGPT compatibility

Two extra actions exist under names ChatGPT's connector platform requires:

ActionWhat it doesPermission
searchSearches photos, and albums as well when album access was granted.Photos · read
fetchRetrieves one photo or album by ID.Photos or Albums · read

They are aliases over the actions above and do nothing the others cannot. Claude and other MCP clients use the specific ones.

Permissions

The consent screen groups permissions by what they touch rather than listing raw scopes. There are six groups, each with a read half and — except for Usage — a write half:

GroupReadWrite
PhotosBrowse, search and open your photosEdit, tag, archive and delete them
AlbumsSee albums, their contents and your share linksCreate, rename, delete and re-fill albums
VideosSee videos and read their transcriptsEdit titles and descriptions, delete videos
Album storiesRead your stories, drafts includedWrite, publish, put on the open web, delete
AccountName, email, plan, equipment, notificationsMark notifications as read
UsageStorage, AI credits, face-recognition quota—

Claude and ChatGPT do not let you tick individual boxes when adding a connector, so a grant is all-or-nothing — the groups exist so that what you are approving is legible before you approve it. Review it on the consent screen; to withdraw everything, remove the connector in the assistant you added it to.

Actions that change data are marked as such in the protocol itself, so a client can ask you to confirm before running one. Deleting a photo, album, video or story is marked more strongly again, and the assistant has to state the intent explicitly before the action will run at all.

Limits and safety

Deletion is permanent. delete_image, delete_album, delete_video and delete_article each require the assistant to confirm the intent explicitly, and none of them can be undone afterwards. Archiving a photo or unpublishing a story is the reversible alternative.

Assistants misread requests. Write access is real access. Grant it to apps you trust, and read what a destructive action says before approving it.

Lists are paginated. Anything that returns a list takes a page number and a page size up to 100, and reports how many results exist in total. If the assistant seems to have seen only part of your library, ask it for the next page.

Some things are deliberately out of reach. Uploading photos or videos, editing photos with AI, and managing billing are not connector actions — they live in the apps and on the website.

RawbackRawbackRawback
HomePricing
Log inSign up