# How to connect SmugMug to OpenClaw (paste one key, 25 tools) > Connect SmugMug to OpenClaw with ClawLink: paste your SmugMug key once and 25 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/smugmug The usual route to SmugMug access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical SmugMug setup: install one ClawHub skill, connect SmugMug in the browser, and OpenClaw can call real SmugMug actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to SmugMug. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect SmugMug** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect smugmug # connect SmugMug (browser OAuth) npx -y @useclawlink/cli actions smugmug # list available actions npx -y @useclawlink/cli run smugmug --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect SmugMug in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your SmugMug API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from SmugMug, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once SmugMug is connected in the dashboard, that agent calls the same 25 SmugMug tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## SmugMug MCP for OpenClaw Looking for a SmugMug MCP server for OpenClaw? ClawLink connects SmugMug to OpenClaw and exposes 25 SmugMug tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes SmugMug integration](https://claw-link.dev/hermes/smugmug) works the same way. ## What the OpenClaw SmugMug integration can do 25 SmugMug tools are ready for OpenClaw once the account is connected. ### All 25 SmugMug tools for OpenClaw | Tool | What it does | |---|---| | **Get album** `smugmug_get_album` | Retrieves detailed information about a SmugMug album using its album key | | **Get album highlight image** `smugmug_get_album_highlight_image` | Retrieves the highlight/cover image for a SmugMug album | | **Get album image** `smugmug_get_album_image` | Get an image within a specific album context as an AlbumImage relationship object | | **Get album images** `smugmug_get_album_images` | Retrieve all images in a SmugMug album as AlbumImage relationship objects | | **Get folder albums** `smugmug_get_folder_albums` | Retrieve albums from a specific folder in a SmugMug user's account by nickname and folder path | | **Get folder by user path** `smugmug_get_folder_by_user_path` | Retrieve folder details by user nickname and folder path | | **Get folder details** `smugmug_get_folder_details` | Retrieves details of a specific folder in SmugMug using its Node ID | | **Get folder subfolders** `smugmug_get_folder_subfolders` | Retrieves all subfolders within a specified folder in a SmugMug user's account | | **Get image** `smugmug_get_image` | Retrieve details for a specific image (photo or video) by its image key | | **Get image metadata** `smugmug_get_image_metadata` | Retrieve additional metadata from an image file including EXIF data, camera settings, GPS | | **Get image size details** `smugmug_get_image_size_details` | Retrieve raw media URLs and dimensions for all available sizes of an image | | **Get image sizes** `smugmug_get_image_sizes` | Retrieves available image sizes and URLs for a SmugMug image by its unique image key | | **Get node highlight image** `smugmug_get_node_highlight_image` | Get the highlight/cover image for a node (folder, album, or page) | | **Get node parent** `smugmug_get_node_parent` | Retrieve the parent node of a specified SmugMug node | | **Get node parents** `smugmug_get_node_parents` | Retrieve a node and all its ancestor nodes (breadcrumb trail) | | **Get user** `smugmug_get_user` | Get a SmugMug user account by their nickname | | **Get user bio image** `smugmug_get_user_bio_image` | Retrieve the bio image for a SmugMug user by their nickname (username) | | **Get user featured albums** `smugmug_get_user_featured_albums` | Retrieves the featured albums for a SmugMug user by their nickname | | **Get user features** `smugmug_get_user_features` | Retrieve a list of features available to a SmugMug user based on their subscription plan | | **Get user profile** `smugmug_get_user_profile` | Retrieves the public profile information for a SmugMug user by their nickname (username) | | **Get user root node** `smugmug_get_user_root_node` | Retrieve the root node of a user's folder tree on SmugMug | | **List child nodes** `smugmug_list_child_nodes` | Lists all child nodes (folders and albums) under a specified parent node in SmugMug | | **Search user content** `smugmug_search_user_content` | Search for images across a user's SmugMug content | | **Unlock album** `smugmug_unlock_album` | Unlock a password-protected SmugMug album | | **Unlock user** `smugmug_unlock_user` | Unlock a user's password-protected SmugMug site | ## Example prompts **Get Album** > Pull the relevant data from SmugMug, summarize it in plain English, and point out anything that needs attention. **Get Album Highlight Image** > Pull the relevant data from SmugMug, summarize it in plain English, and point out anything that needs attention. **Get Album Image** > Pull the relevant data from SmugMug, summarize it in plain English, and point out anything that needs attention. **Get Album Images** > Pull the relevant data from SmugMug, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want SmugMug working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the SmugMug API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected SmugMug account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for SmugMug. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right SmugMug actions to the runtime in a format your agent can reliably use. | 25 tools for SmugMug are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes SmugMug to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect SmugMug in the browser, and the 25 tools above work from chat. There is no SDK and no config file, and the SmugMug key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the SmugMug skill but can't call the tools The ClawHub skill teaches OpenClaw about SmugMug, but the calls run through the ClawLink plugin and your connected account. Make sure SmugMug is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect SmugMug from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling SmugMug tools SmugMug tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every SmugMug call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### SmugMug returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for SmugMug has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw SmugMug integration? Yes. ClawLink is the fastest way to connect OpenClaw to SmugMug: link your SmugMug account once in the browser and OpenClaw can call the SmugMug API through 25 ready-made tools — no custom code or token handling. ### How do I add SmugMug to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink SmugMug skill from ClawHub, then you click Connect in the dashboard to authorize SmugMug. OpenClaw calls the tools from the next message — no config files, and the SmugMug key you paste is stored server-side instead of in your environment. ### How long does it take to connect SmugMug to OpenClaw? About two minutes. Sign in, click Connect next to SmugMug in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring SmugMug up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want SmugMug working from chat. ### OpenClaw installed the SmugMug skill but can't call the tools The ClawHub skill teaches OpenClaw about SmugMug, but the calls run through the ClawLink plugin and your connected account. Make sure SmugMug is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [OpenClaw Box integration](https://claw-link.dev/openclaw/box) — Store, share, and manage files and folders - [OpenClaw Supabase integration](https://claw-link.dev/openclaw/supabase) — Query and manage Postgres databases - [Dropbox](https://claw-link.dev/openclaw/dropbox) — Store, sync, and share files