Skip to main content
Glama
vmayfuture

网易春风 · 心跳元力 MCP

by vmayfuture
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to 网易春风 · 心跳元力 MCP

No user-submitted related servers found.

    Related Servers

    • mcp-ble-bridge

      kumavulp
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control Bluetooth Low Energy devices remotely through a WebSocket and Web Bluetooth bridge, exposing tools for vibration, suction, licking, pulsing, and status checks.
      -

    • VectorClaw

      danmartinez78
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to control Anki Vector robots locally via natural language, providing tools for speech, motion, perception, and interaction without cloud dependency.
      24
      20
      MIT

    • G1 UART MCP Server

      danroblewis
      A
      license
      A
      quality
      D
      maintenance
      Enables communication with G1 Bluetooth devices using the Nordic UART protocol over BLE. Supports device discovery, connection management, and message exchange for G1 audio devices through natural language commands.
      5
      2
      MIT

    • Miji BLE MCP Server

      Gaoshu705
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for controlling BLE-enabled adult toys from XHTKJ and 醉清风 mini-programs, enabling strength, mode, and custom waveform control via natural language.
      6
      -

    • MCP Casambi

      nkapila6
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables control of lights in CASAMBI networks through Bluetooth interface without requiring APIs. Provides direct lighting control and management capabilities through natural language interactions.
      1
      GPL 3.0
    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

    B3.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a distinct role across the BLE lifecycle: discovery, connection, status, modality-specific output control, stopping outputs, and disconnection. The three set_* tools are clearly separated by vibration, linear, and rotary outputs, while stop_device and disconnect_device are distinguishable by scope.

    Naming Consistency5/5

    All tool names use consistent snake_case with verb_noun or verb_noun_noun structure. list_devices, connect_device, get_device_status, set_vibration, set_linear, set_rotary, stop_device, and disconnect_device follow the same predictable convention.

    Tool Count5/5

    Eight tools are well-scoped for a BLE device control server. The set covers discovery, connection management, status inspection, three independent output modes, emergency stop, and disconnect without unnecessary bloat.

    Completeness4/5

    The surface covers the core device control lifecycle and operation modes well. Minor gaps remain around reading current output intensities or device telemetry such as battery/firmware, but agents can complete the main workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources