How to integrate Smugmug MCP with Mastra AI

Trusted by
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Smugmug logo
Mastra AI logo
divider

Introduction

This guide walks you through connecting Smugmug to Mastra AI using the Composio tool router. By the end, you'll have a working Smugmug agent that can show all albums in your travel folder, get details for the europe 2023 album, list all child folders under weddings through natural language commands.

This guide will help you understand how to give your Mastra AI agent real control over a Smugmug account through Composio's Smugmug MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Smugmug with

TL;DR

Here's what you'll learn:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Smugmug tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Smugmug tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Smugmug agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

What is the Smugmug MCP server, and what's possible with it?

The Smugmug MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Smugmug account. It provides structured and secure access to your photo galleries and user profile, so your agent can perform actions like browsing folders, listing albums, retrieving photo details, and exploring your Smugmug structure on your behalf.

  • Retrieve folder and album details: Instantly fetch information about specific folders or albums, including creation dates, node IDs, and highlight albums.
  • Explore your Smugmug hierarchy: Ask your agent to list all child nodes—albums or folders—within any parent node, helping you navigate your photo organization with ease.
  • List albums in any folder: Let your agent pull comprehensive lists of albums within a designated folder, even handling large collections with pagination.
  • Get public user profile info: Retrieve your Smugmug public profile details to share or review your online photography presence.
  • Access node-specific data: Have your agent look up details for any node (album, folder, or page) using its unique identifier, supporting granular photo management and discovery.

Supported Tools & Triggers

Tools
Get AlbumRetrieves detailed information about a SmugMug album using its album key.
Get Album Highlight ImageRetrieves the highlight/cover image for a SmugMug album.
Get Album ImageGet an image within a specific album context as an AlbumImage relationship object.
Get Album ImagesTool to retrieve all images in a SmugMug album as AlbumImage relationship objects.
Get Folder AlbumsTool to retrieve albums from a specific folder in a SmugMug user's account by nickname and folder path.
Get Folder by User and PathTool to retrieve folder details by user nickname and folder path.
Get Folder DetailsRetrieves details of a specific folder in SmugMug using its Node ID.
Get Folder SubfoldersRetrieves all subfolders within a specified folder in a SmugMug user's account.
Get ImageTool to retrieve details for a specific image (photo or video) by its image key.
Get Image MetadataTool to retrieve additional metadata from an image file including EXIF data, camera settings, GPS location, and other embedded information.
Get Image Size DetailsRetrieve raw media URLs and dimensions for all available sizes of an image.
Get Image SizesRetrieves available image sizes and URLs for a SmugMug image by its unique image key.
Get Node Highlight ImageTool to get the highlight/cover image for a node (folder, album, or page).
Get Node ParentTool to retrieve the parent node of a specified SmugMug node.
Get Node ParentsTool to retrieve a node and all its ancestor nodes (breadcrumb trail).
Get UserTool to get a SmugMug user account by their nickname.
Get User Bio ImageTool to retrieve the bio image for a SmugMug user by their nickname (username).
Get User Featured AlbumsRetrieves the featured albums for a SmugMug user by their nickname.
Get User FeaturesTool to retrieve a list of features available to a SmugMug user based on their subscription plan.
Get User ProfileRetrieves the public profile information for a SmugMug user by their nickname (username).
Get User Root NodeTool to retrieve the root node of a user's folder tree on SmugMug.
List Child NodesLists all child nodes (folders and albums) under a specified parent node in SmugMug.
Search User ContentSearch for images across a user's SmugMug content.
Unlock AlbumTool to unlock a password-protected SmugMug album.
Unlock User SiteTool to unlock a user's password-protected SmugMug site.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Smugmug through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for Smugmug

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["smugmug"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Smugmug MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "smugmug" for Smugmug access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Smugmug toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "smugmug-mastra-agent",
    instructions: "You are an AI agent with Smugmug tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        smugmug: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Smugmug toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Smugmug and Mastra AI:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["smugmug"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      smugmug: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "smugmug-mastra-agent",
    instructions: "You are an AI agent with Smugmug tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { smugmug: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Smugmug through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

How to build Smugmug MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Smugmug MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Smugmug MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Smugmug MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Smugmug MCP with Claude Cowork

Codex logo

Codex

Use Smugmug MCP with Codex

OpenClaw logo

OpenClaw

Use Smugmug MCP with OpenClaw

Hermes logo

Hermes

Use Smugmug MCP with Hermes

CLI logo

CLI

Use Smugmug MCP with CLI

Google ADK logo

Google ADK

Use Smugmug MCP with Google ADK

LangChain logo

LangChain

Use Smugmug MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Smugmug MCP with Vercel AI SDK

LlamaIndex logo

LlamaIndex

Use Smugmug MCP with LlamaIndex

CrewAI logo

CrewAI

Use Smugmug MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Smugmug MCP?

With a standalone Smugmug MCP server, the agents and LLMs can only access a fixed set of Smugmug tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Smugmug and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Mastra AI?

Yes, you can. Mastra AI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Smugmug tools.

Can I manage the permissions and scopes for Smugmug while using Tool Router?

Yes, absolutely. You can configure which Smugmug scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Smugmug data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Get started for freeGet a demo↗