Skip to main content
Glama
benjamin-di

photos-mcp

by benjamin-di
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to photos-mcp

No user-submitted related servers found.

    Related Servers

    • gphotos-mcp

      vsmelov
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to a personal Google Photos library, allowing listing, searching, inspecting, and viewing photos and albums via MCP tools.
      -

    • Google Photos MCP

      thenavidm
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to work with a user's Google Photos through Google's picker, letting users choose exactly what the agent sees while providing tools for uploading media, creating and sharing albums, writing captions and enrichments, searching app-created media, and managing multiple Google accounts.
      29
      44 npm
      1
      MIT

    • gsc-readonly-mcp

      brodesigns
      A
      license
      A
      quality
      A
      maintenance
      Enables read-only access to Google Search Console data, including search analytics, sitemap status, URL inspection, and property listing.
      4
      7 npm
      MIT

    • imogen

      ergofobe
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to search a self-hosted photo and video library, view photos, and manage albums through MCP, with all actions scoped to the connected account and vault items hidden.
      1
      AGPL 3.0

    • GSC MCP

      muryulia
      A
      license
      A
      quality
      B
      maintenance
      Enables read-only access to Google Search Console data, including property discovery, search analytics queries, and URL inspection, through a security-focused interface.
      3
      106 PyPI
      1
      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

    A3.9/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target clearly distinct resources or actions, especially the album CRUD, trash/restore, upload, and search/list/get families. Minor overlap exists among the visual presentation tools (photos_contact_sheet, photos_view, photos_show) and between photos_status and photos_canary, though descriptions mostly disambiguate them.

    Naming Consistency4/5

    All tool names use the photos_ prefix and snake_case, which makes the set predictable and readable. The pattern is mostly action-oriented but includes noun-first resource forms like photos_album_add and noun tools like photos_status, so it is not a pure verb_noun convention throughout.

    Tool Count4/5

    Seventeen tools is slightly above the ideal lightweight range, but the Google Photos domain is broad enough to justify search, listing, albums, trash, upload, display, and health checks. Each tool appears to earn its place rather than being redundant filler.

    Completeness4/5

    The surface covers core photo lifecycle operations: search/list/get, album create/add/remove/delete/list, trash/restore, upload, presentation, and monitoring. Minor gaps remain, such as not obviously listing trashed items and no album rename/update operation, but agents can work around these for most workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources