SmugMug MCP integration for AI agents.
Connect AI agents to SmugMug through 23 structured actions, including get album, get album highlight image, and get album image. Review authentication, input…
- ACTION CONTRACTS
- 23
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the SmugMug integration exposes
The SmugMug Agent App exposes 23 provider-backed actions for design and storage work. Its current contract lets an authorized agent retrieve a smugmug album by key, retrieve the highlight image for a smugmug album, and retrieve a smugmug album image relationship. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected SmugMug account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real SmugMug capabilities.
Showing 12 of 23 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_albumREADRetrieve a SmugMug album by key.
INPUTS: albumKey
get_album_highlight_imageREADRetrieve the highlight image for a SmugMug album.
INPUTS: albumKey
get_album_imageREADRetrieve a SmugMug album image relationship.
INPUTS: albumKey / imageKey
get_album_imagesREADList images in a SmugMug album.
INPUTS: albumKey / count / start
get_folder_albumsREADList albums below a SmugMug folder path.
INPUTS: nickname / folderPath / folderId
get_folder_by_user_pathREADResolve a SmugMug folder by user nickname and path.
INPUTS: nickname / folderPath / folderId
get_folder_detailsREADRetrieve details for a SmugMug folder node.
INPUTS: nodeId
get_folder_subfoldersREADList subfolders below a SmugMug folder path.
INPUTS: nickname / folderPath / folderId
get_imageREADRetrieve a SmugMug image by key.
INPUTS: imageKey
get_image_metadataREADRetrieve metadata for a SmugMug image.
INPUTS: imageKey
get_image_size_detailsREADRetrieve full image size details for a SmugMug image.
INPUTS: imageKey
get_image_sizesREADList direct image size URLs for a SmugMug image.
INPUTS: imageKey
INPUT CONTRACTS
Know what the action needs before it runs.
get_album
albumKeyREQUIRED- The SmugMug album key.
get_album_highlight_image
albumKeyREQUIRED- The SmugMug album key.
get_album_image
albumKeyREQUIRED- The SmugMug album key.
imageKeyREQUIRED- The SmugMug image key.
get_album_images
albumKeyREQUIRED- The SmugMug album key.
countOPTIONAL- The number of results to return per page.
startOPTIONAL- The 1-based start index for pagination.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Album
Retrieve a SmugMug album by key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_albumVerify with Get Album Highlight Image
Retrieve the highlight image for a SmugMug album. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_album_highlight_imageSAFETY BOUNDARY
Operate SmugMug with explicit limits
- Authorize SmugMug with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned SmugMug data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in SmugMug rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the SmugMug task completed successfully.
CONNECTION MODEL
API key
SmugMug API key used for public API access via the APIKey query parameter. Request it here: https://api.smugmug.com/api/developer/apply
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 23
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by SmugMug.