TriCaster MCP Server
Related Servers
Alternatives to TriCaster MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP (Model Context Protocol) server for controlling OBS Studio via the built-in obs-websocket plugin. Lets Claude control your scenes, recording, streaming, audio, and more.266 npm1MIT
- FlicenseAqualityBmaintenanceAn MCP server that gives Claude Code hands inside DaVinci Resolve Studio, enabling project management, status checks, snapshots, and arbitrary Python scripting via the Resolve API.51-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables Claude to control Ableton Live in real-time via the AbletonOSC bridge. It allows users to manage playback, create tracks, write MIDI, and adjust mixer or device parameters using natural language commands.-
- FlicenseAqualityDmaintenanceMCP server that lets Claude control Google Gemini Omni video generation via a browser bridge (Playwright) until the official API ships.3-
- FlicenseNot gradedqualityCmaintenanceMCP server exposing claude-video functionality for claude.ai web UI via HTTP+SSE, enabling video watching and analysis from claude.ai.-
- AlicenseNot gradedqualityBmaintenanceAn MCP server that connects Claude to FL Studio, enabling natural language control of transport, mixer, channel rack, and piano roll operations.MIT
TDQS
Scored across 35 tools
Tools are mostly distinct with clear resource+action pairs, such as set_audio_volume vs set_audio_mute, and ddr_play vs ddr_stop. Minor confusion may arise between switch_program, cut_transition, and auto_transition, as well as fade_to_black vs take_to_black, but descriptions clarify the differences. Overall, misselection risk is low.
Most names follow a consistent snake_case verb_noun pattern (e.g., set_audio_volume, get_ddr_status, start_record). Deviations like ddr_play, dsk_on, and auto_transition break the verb-first convention, but the set remains readable and predictably grouped by prefix (ddr_, dsk_).
With 35 tools, the count is heavy and exceeds typical well-scoped ranges, though the TriCaster's many subsystems (audio, video, streaming, macros, etc.) justify some breadth. Some generic tools like get_dictionary and send_shortcut overlap with specific getters, suggesting potential consolidation. The set feels borderline overloaded.
Coverage is strong across major operations: audio, DDR, media browsing, macros, DSK, recording, streaming, transitions, and switcher state. Gaps include macro creation/deletion and fine-grained DSK or audio configuration, but core lifecycle actions are well represented.