Skip to main content
Glama
flix-pro

Flix MCP Server

Official
by flix-pro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Flix MCP Server

No user-submitted related servers found.

    Related Servers

    • modelmux

      JRWoodcock
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      4
      6 npm
      Apache 2.0

    • Converse MCP Enhanced

      justmy2satoshis
      A
      license
      Not graded
      quality
      D
      maintenance
      Multi-model AI conversation MCP for Claude Desktop. Seamlessly integrate with GPT-4, Gemini, xAI, Perplexity, and local models via Ollama.
      MIT

    • claude-c2

      0xyg3n
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language command and control of remote systems across multiple platforms through Claude AI using the Model Context Protocol.
      8
      -

    • Cursor MCP Server

      johnneerdael
      A
      license
      Not graded
      quality
      D
      maintenance
      Acts as a bridge between Claude's desktop application and the Cursor editor, enabling seamless AI-powered automation and multi-instance management across platforms with standardized communication and secure token-based authentication.
      4 npm
      68
      MIT

    • claude-nexus

      skyvanguard
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code instances to discover each other and exchange messages instantly via a local broker and channel protocol. Supports scoped peer discovery, reliable ack-based delivery, and cross-platform operation.
      3 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 16 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources