Skip to main content
Glama
mediagraph-io

Mediagraph MCP

Official
by mediagraph-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Mediagraph MCP

No user-submitted related servers found.

    Related Servers

    • mcp-openverse

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for searching and retrieving Creative-Commons-licensed images and audio from Openverse. Enables AI agents to query open media content.
      10 npm
      MIT

    • inmydata MCP Server

      inmydata
      F
      license
      Not graded
      quality
      B
      maintenance
      Exposes the inmydata agents SDK as an MCP server, enabling AI agents to access inmydata's powerful data querying capabilities through a standardized interface.
      -

    • asset-mcp

      Gollum-code
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a local creator asset library MCP server that scans folders to catalog media files, batch-renames them, applies tags, tracks asset lineage between source and finished works, and offers keyword- and BGE-vector-based semantic search. It also lets other content-production MCP servers auto-register their generated outputs into the library for later retrieval and reuse.
      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

    C2.6/5.0

    Scored across 276 tools

    Disambiguation2/5

    Many tools have overlapping or near-identical purposes: search_assets vs search_assets_visual, update_asset vs bulk_edit_assets vs set_asset_custom_meta vs update_asset_description, and a dense cluster of face/tagging tools (tag_asset_face, associate_tagging_with_face, set_main_face_for_tagging, set_tag_face_creator_tag, set_tag_face_membership) that are hard to distinguish without deep domain knowledge. Invite/share/access-request/contribution concepts also fragment into dozens of similarly named tools (create_share vs create_share_link vs create_invite vs create_contribution), making misselection likely.

    Naming Consistency4/5

    Nearly everything is snake_case verb_noun (list_tags, create_collection, delete_webhook), with consistent bulk_/get_/list_/create_/update_/delete_ prefixes. Minor deviations exist: whoami, reauthorize, and the mix of find_* vs get_* for lookups, but the convention remains readable and predictable.

    Tool Count1/5

    276 tools is an extreme surface far beyond what an agent can navigate reliably; many are super-admin, diagnostic, or one-off maintenance operations (mark_organization_cai_invoice_paid, explain_asset_search, get_pending_membership_requests_count). The set should be split into narrower servers or consolidated.

    Completeness4/5

    The DAM domain is covered comprehensively: asset CRUD/versioning/restore, tags, taxonomies, collections, lightboxes, storage folders, shares, access requests, workflows, webhooks, uploads, contributions, bulk jobs, and meta import/export. Minor gaps exist (no update/delete for rights packages, some lifecycle actions only partially covered), but core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources