Skip to main content
Glama
Pixifi MCP Server

Pixifi MCP Server

Related Servers

Alternatives to Pixifi 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
      A
      quality
      B
      maintenance
      Connects ChatGPT, Claude and other AI agents to your own signed-in oto.photo account, letting them read and update client galleries, bookings, client lists, gift certificates and portfolio albums, asking for confirmation before most changes. Uploads, deletions, encrypted albums and client messaging stay outside its reach.
      7
      Elastic 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables ChatGPT, Claude, and AI agents to work with contacts, projects, offers, invoices, and working hours in a signed-in Plancraft account, with approval required by default for sending documents, recording payments, and booking hours.
      7
      Elastic 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables ChatGPT, Claude and other AI agents to manage availability, blocked time, forms, invoices and client reports in a signed-in account, with write actions requiring approval by default. It connects through Cotlet.dev either as a hosted endpoint or as a local stdio server that forwards tool calls.
      7
      Elastic 2.0

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct role in the browser workflow: guidance, readiness check, session opening, page reading, clicking, typing, and closing. There is little risk of confusing one tool for another, especially because read/click/type operate on numbered page elements.

    Naming Consistency5/5

    All tools use a consistent pixifi_ prefix followed by a short snake_case action or state label. Although guide and status are noun-like rather than pure verbs, the overall naming convention is predictable and easy to scan.

    Tool Count5/5

    Seven tools is well-scoped for a browser-automation surface: guide and status support setup, open/read/click/type cover the core interaction loop, and close handles cleanup. No tool appears redundant.

    Completeness4/5

    The set covers the essential browser lifecycle and interaction primitives needed to work inside Pixifi. Minor gaps exist, such as explicit navigation, scrolling, select/dropdown handling, or upload/download support, but most workflows can be worked around via read/click/type.