Skip to main content
Glama
Sign In
findme-mcp

findme-mcp

Official
by findmephoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to findme-mcp

No user-submitted related servers found.

    Related Servers

    • SmugMCP

      cotlet-connect
      A
      license
      A
      quality
      C
      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
      Elastic 2.0

    • Pixieset MCP Server

      cotlet-connect
      A
      license
      Not graded
      quality
      C
      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.
      Elastic 2.0

    • flickr-mcp

      MK3Core
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to access, tag, describe, and manage a Flickr photo library, including automated batch processing.
      61 npm
      1
      MIT

    • wedding30s

      wedding30s
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to draft wedding invitation websites by creating unpaid drafts, listing templates, and retrieving pricing information.
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools map to a distinct resource and action, with clear separation between event CRUD, upload flows, analytics, and account/usage. The main ambiguity is get_event vs get_event_analytics, since both report guest visits and selfie searches, and get_usage vs get_account_info are both account-level but cover different data.

    Naming Consistency5/5

    All 14 tools follow a consistent snake_case verb_noun pattern: get_*, create_*, list_*, update_*, delete_*, restore_*, and upload_photos_from_*. Composite names like get_event_qr and get_event_analytics fit the same predictable style without mixing conventions.

    Tool Count5/5

    14 tools is well within the ideal range for an event/gallery management server, and each tool has a clear operational purpose. The count feels complete without being bloated: usage, account context, event lifecycle, upload entry points, analytics, and QR access are all covered.

    Completeness4/5

    Event CRUD is thoroughly covered including soft-delete and restore, and uploads are supported via local paths, URLs, Drive, and a no-login link. The notable gap is direct per-photo management—listing, removing, or editing individual photos after upload—but agents can work around it through the gallery URL and upload link.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources