Skip to main content
Glama

Related Servers

Alternatives to Wistia MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to manage Vimeo video libraries through natural language, including bulk folder operations, transcripts, chapters, captions, showcases, tags, privacy, and embed presets.
      43
      124 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes the full Chatwoot API as 129 tools for AI assistants, enabling account, contact, conversation, message, inbox, team, report, help center, automation, and custom attribute management, plus exclusive Kanban and scheduled message features.
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Gives AI coding agents full control over a YouTube channel with 22 tools for channel management, videos, playlists, comments, search, analytics, thumbnails, and captions.
      10 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to fully automate Appwrite backend operations with 143 tools covering databases, users, storage, functions, messaging, and more. Supports advanced features like GeoJSON attributes, file uploads, function deployment, and bulk operations.
      3 npm
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with the full Odichat API, providing 123 tools for managing accounts, agents, contacts, conversations, inboxes, reports, and Odichat-exclusive features like Kanban boards and scheduled messages.
      MIT

    TDQS

    B3.1/5.0

    Scored across 169 tools

    Disambiguation2/5

    There are clear duplicates and near-duplicates: upload_media and upload_media_file have identical descriptions, get_media_stats and get_media_stats_stats_media appear to do the same thing, and get_media_analytics/get_media_stats/get_media_stats_by_date/get_media_engagement overlap heavily. With 169 tools across media stats, analytics, and customization concerns, an agent faces many ambiguous choices between similarly-purposed endpoints.

    Naming Consistency3/5

    Most tools follow a snake_case verb_noun pattern (list_media, create_folder, update_channel), but there are deviations like 'bulk_tag' (verb omitted), 'un_publish_channel_episode' (underscore variant), 'get_media_stats_stats_media' (garbled), and inconsistent list_captions vs list_all_captions vs list_all_captions/list_channel_episodes vs list_channel_episodes_by_channel. Readable but not fully predictable.

    Tool Count1/5

    169 tools is far beyond any reasonable scope for effective tool selection, and the surface is bloated with redundant variants (multiple stats endpoints, duplicated customizations get/update pairs, upload_media vs upload_media_file). The count creates selection burden that defeats the purpose of a coherent toolset.

    Completeness4/5

    Coverage is extensive: full CRUD across media, folders, subfolders, channels, episodes, webinars, captions, localizations, brands, shares, tags, and collaborators, plus rich analytics. Minor gaps exist (e.g., no media creation via bulk actions, some resources lack full lifecycle), but the domain surface is essentially complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues