Skip to main content
Glama

Related Servers

Alternatives to SlickPic MCP server

No user-submitted related servers found.

    Related Servers

    • 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
      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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to open and interact with web pages in isolated cloud browser sessions, including clicking, typing, reading, uploading and downloading files, handling email, and using developer tools, while a live view lets users watch and take over for logins or captchas.
      MIT

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: guide/status are informational/setup, while open/read/click/type/close form an unambiguous browser interaction loop. There is little risk of an agent confusing one tool for another.

    Naming Consistency5/5

    All seven tools use lowercase snake_case with the same slickpic_ prefix and short, predictable labels. The only slight variation is guide/status as state/info labels, but the naming remains consistent overall.

    Tool Count5/5

    Seven tools is a well-scoped set for browser-based SlickPic automation: setup, session open/close, page reading, and clicking/typing. Each tool earns its place without obvious redundancy.

    Completeness4/5

    The core lifecycle is covered: onboarding/status, opening a page, reading it, interacting via click/type, and closing the session. Minor gaps exist for advanced browser actions such as explicit navigation, waiting, or file upload, but the main workflow is supported.