A
licenseNot graded
qualityC
maintenanceEasily build MCP tools for Claude desktop app.
132 npm
21
MIT
Catalyst MCP for FiveM
by Geckomacabre
Related Servers
Alternatives to Catalyst MCP for FiveM
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI-powered control of Blender through natural language, allowing users to create, manipulate, and automate 3D scenes, objects, materials, animations, and more via Claude or other MCP clients.7165MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives Claude a conversational video-editing toolkit — trim, crop, color grade, caption, beat-sync, stabilize, and more — built on ffmpeg, faster-whisper, and yt-dlp, with optional DaVinci Resolve and CapCut integration.2MIT
- FlicenseNot gradedqualityDmaintenanceA local MCP server that gives Claude Desktop full video editing capabilities via FFmpeg, Whisper, and yt-dlp.-
- AlicenseBqualityDmaintenanceAn MCP server that lets Claude read and edit CapCut desktop draft projects, enabling manipulation of video clips, text, audio, and images with atomic saves and validation.1719MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients such as Claude Desktop and Cursor to generate images and videos, synthesize speech, clone voices, and design custom voices from descriptive prompts. It supports stdio, REST, and SSE transport modes with configurable API hosts, keys, and local or URL-based resource output.493 npmMIT
TDQS
A3.6/5.0
Scored across 10 tools
Disambiguation4/5
Each tool maps to a distinct step of the particle-dictionary pipeline (unpack/pack/edit/merge/info/install), so pairwise confusion is low. The only soft overlap is ptfx_vanilla_search, which already returns the cached .ypt that ptfx_vanilla_get also returns, plus ptfx_info vs ptfx_unpack both surfacing dictionary contents.
Naming Consistency4/5
Nine of ten tools use a consistent ptfx_ snake_case verb-or-noun suffix pattern. catalyst_open breaks the prefix convention and inverts to noun_verb, a minor but visible deviation.
Tool Count5/5
Ten tools is well within the sweet spot and every one earns its place: the vanilla index/search/get trio, the unpack/merge/edit/pack authoring chain, install, and preview. No filler or redundant wrappers.
Completeness4/5
The surface covers the full lifecycle from vanilla discovery through merge, edit, pack with verify, install to a resource, and preview. Minor gaps: no tool to list or remove already-installed .ypt files from a resource, and no standalone validation/report tool outside ptfx_pack's verify flag.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues