srgplus-mcp
OfficialRelated Servers
Alternatives to srgplus-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for the digihub.li content API, enabling Claude to read and write Stories, Solutions, and Sessions, and upload images for media.177 npmMIT
- AlicenseAqualityCmaintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.870,822 npmMIT
- -licenseNot gradedqualityAmaintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.70,822 npm90,569MIT
- AlicenseAqualityBmaintenanceMCP Server for the Mattermost API, enabling Claude and other MCP clients to interact with Mattermost workspaces.969 npm3MIT
- AlicenseAqualityBmaintenanceMCP Server for the Notion API, enabling Claude to interact with Notion workspaces.31850 npm922MIT
- AlicenseAqualityDmaintenanceA local stdio MCP server that gives Claude (or any MCP client) full programmatic control over a single YouTube channel, including video upload, channel management, comments, analytics, and more.4619 npmMIT
TDQS
Scored across 103 tools
Most tools have distinct purposes, but the high number of similar CRUD operations (e.g., create_hub_profile vs create_channel vs create_category, get_channel_by_name vs get_channel) could cause confusion. The descriptions are detailed enough to differentiate, though some overlap exists between content/category/section operations.
The naming convention is mostly consistent with verb_noun patterns (list_, get_, create_, update_, delete_, etc.), but there are some deviations like `can_read`, `can_edit`, `is_member`, and `get_srgplus_guide` that don't fit the typical CRUD pattern. The mix of `list_*` and `get_*` for similar operations is slightly inconsistent.
With 103 tools, this is a very large surface area. While the domain is broad (workspaces, hub profiles, channels, categories, sections, content, assets, users, permissions, invitations, automation actions), the sheer number makes navigation difficult. Many tools are near-duplicates (e.g., multiple invitation link generators, multiple permission checkers), suggesting the count could be trimmed.
The tool set appears to cover the full lifecycle of the platform: workspace management, hub profile management, content hierarchy (channel→category→section→content), asset upload, user/permission management, invitations, automation actions, and permission groups. Missing features like content deletion are intentional (archiving instead), and the guide tool fills knowledge gaps.