A
licenseNot graded
qualityC
maintenanceMCP server for searching and retrieving Creative-Commons-licensed images and audio from Openverse. Enables AI agents to query open media content.
2 npm
MIT
Mediagraph MCP
OfficialRelated Servers
Alternatives to Mediagraph MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceExposes the inmydata agents SDK as an MCP server, enabling AI agents to access inmydata's powerful data querying capabilities through a standardized interface.-
- FlicenseNot gradedqualityCmaintenanceExposes multimodal analysis tools (text search, image metadata/captions, audio features, video frame sampling) over a local media store via MCP, and includes an optional CrewAI Router/Specialist/Responder client that routes requests by modality.-
Runware MCPofficial
AlicenseNot gradedqualityBmaintenanceMCP server that gives AI agents access to Runware's full API for image, video, audio, 3D, upscaling, and other media generation and processing tasks via natural language.123 npmMIT- AlicenseAqualityAmaintenanceMCP server exposing NaN API media tools (image generation/editing, text-to-speech, speech-to-text, embeddings, reranking) for any MCP-compatible client.8476 npm7MIT
- AlicenseAqualityDmaintenanceMCP server that provides image generation, captioning, and tagging via ComfyUI API, configurable for agent tools.43MIT
TDQS
C2.5/5.0
Scored across 276 tools
Disambiguation2/5
With 276 tools, many have overlapping or subtly different purposes (e.g., list_shares vs list_share_links, ignore_asset_unidentified_faces vs ignore_asset_face_toggle, get_recent_tag_events vs get_tag_events), making misselection likely. The detailed descriptions help, but the sheer volume and near-duplicate operations create significant ambiguity.
Naming Consistency4/5
The overwhelming majority follow a consistent verb_noun snake_case pattern (list_*, get_*, create_*, update_*, delete_*), which is predictable and readable. Minor deviations like whoami, reauthorize, can_upload, and explain_asset_search are few and do not undermine the overall pattern.
Tool Count1/5
276 tools is an extreme number for any MCP server, far exceeding the 50+ threshold. Even for a comprehensive DAM system, this is an unwieldy and poorly scoped tool surface that would overwhelm agents and require excessive context.
Completeness3/5
Many domains have solid CRUD coverage (assets, collections, lightboxes, tags, workflows, comments, webhooks), but notable gaps exist: storage folders have no update/delete, rights packages have no update/delete, crop presets lack update/delete, invites have no delete/revoke, and meta imports/ingestions are read-only. Workflow steps also lack a reject action, and notifications have no mark-as-read.
Maintenance
ActivityInactive
ResponsivenessNo issues