Flix MCP Server
OfficialRelated Servers
Alternatives to Flix MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables Claude Code to call local generative AI services on a LAN, letting users list and chat with Ollama models and list checkpoints, LoRAs, and samplers or generate and save images via Stable Diffusion WebUI Forge Neo. Requests can be made in natural language, with per-call options for model, image size, and Hires.fix settings.1MIT
- AlicenseAqualityCmaintenanceEnables AI agents like Claude Code, Codex, and Perplexity to call each other as tools directly from the terminal, supporting text, code, images, and PDFs passed by file path.48 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables Claude Desktop and Claude Code to call models on a Pico AI Server via a local stdio MCP connection. Provides tools for checking server connectivity, listing and comparing models, and generating responses through Responses, chat completions, and Ollama chat APIs.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents and terminal users to dispatch local files directly to paired mobile phones or other peers over Blip's end-to-end encrypted peer-to-peer transfer, automatically discovering paired devices and avoiding desktop confirmation prompts. It also exposes tools to list paired devices and report daemon health and recent transfer history.MIT
- AlicenseNot gradedqualityDmaintenanceMulti-model AI conversation MCP for Claude Desktop. Seamlessly integrate with GPT-4, Gemini, xAI, Perplexity, and local models via Ollama.MIT
- FlicenseNot gradedqualityDmaintenanceEnables natural language command and control of remote systems across multiple platforms through Claude AI using the Model Context Protocol.8-
TDQS
Scored across 16 tools
Each tool targets a distinct action on a distinct resource: device discovery/info, pairing, blocking, messaging, file transfer control, and clipboard sync. Even paired tools like send_text/send_file or sync_clipboard/get_clipboard are clearly separated by purpose, leaving no ambiguity.
All tool names follow a uniform flix_<verb>_<noun> pattern, with consistent verb choices like get, send, pair, block. The prefix and structure are predictable, making it easy to infer behavior from the name alone.
16 tools might exceed the typical 3-15 range, but each tool earns its place in a comprehensive device management server. The count is well-scoped across six logical domains (discovery, pairing, blocking, messaging, file transfer, clipboard) with no redundant tools.
The tool surface covers the full lifecycle for device interactions: discover, pair, block, send/receive text and files, manage transfers (status/cancel/pause/resume), and sync clipboard. No obvious gaps for the stated purpose of controlling and communicating with Flix devices.