Skip to main content
Glama

Related Servers

Alternatives to oto.photo MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables ChatGPT, Claude, and other AI agents to read and manage clients, photography sessions, contracts, and invoices in a signed-in Iris Works account, including creating drafts and saving changes only after user approval.
      7
      Elastic 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to operate a user's signed-in Pixieset account through natural language, including delivering galleries, booking sessions, sending contracts and invoices, and following up with clients without requiring a Pixieset API key.
      7
      379 PyPI
      Elastic 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects a signed-in CloudSpot account to ChatGPT, Claude, Codex and Claude Code so agents can read galleries and collection analytics, and create collections, deliver images, manage clients, projects, contracts, questionnaires, invoices, mini-sessions, bookings and pending print orders. Writes require confirmation by default, and an optional local stdio bridge adds browser helpers for driving the CloudSpot UI.
      Elastic 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables ChatGPT, Claude, and AI agents to read Salonized appointments, customers, waiting list, notes, and sales reports, while requiring approval before writes or customer notifications.
      Elastic 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to manage a user's own SmugMug account in plain language — creating and securing galleries, auditing visits, renaming and organizing photos, and applying price lists — without needing a SmugMug API key, OAuth setup, or code.
      7
      95 PyPI
      Elastic 2.0

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation4/5

    The core action tools (open, read, click, type, close) are clearly distinct, and guide vs status are separated by their descriptions (instructions vs account/credit check). There is mild conceptual overlap between read, guide and status as all returning information, but the descriptions resolve it.

    Naming Consistency5/5

    Every tool follows the same oto_photo_<verb> snake_case pattern with short, concrete verbs. No mixed conventions or vague naming.

    Tool Count5/5

    Seven tools is well-scoped for a browser-driven site controller: session lifecycle, page inspection, and two input primitives plus help/status. Each tool earns its place with no redundancy.

    Completeness3/5

    The basic interaction loop (open, read, click, type, close) plus guide/status is covered, but there is no scrolling, navigation/back, waiting for loads, or dropdown/checkbox handling, which are likely needed for gallery, booking and client workflows. Photo/album management arguably also implies upload/delete affordances not present.