Skip to main content
Glama
joncady

okabebot-mcp

by joncady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to okabebot-mcp

No user-submitted related servers found.

    Related Servers

    • Device MCP Server

      akshitsinha
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for seamless integration with peripheral devices connected to your computer. Control, monitor, and manage hardware devices through a unified API.
      5
      MIT

    • smart-hardware-bridge

      CJX0712
      A
      license
      Not graded
      quality
      B
      maintenance
      A unified MCP bridge server that lets WorkBuddy and any MCP client control real-world hardware over MQTT and HTTP — reading device state and sending commands through natural language, with a pluggable adapter layer for adding new protocols.
      MIT

    • embodify-mcp

      YidaYang
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-capable agents to see and control robots directly by listing tasks, starting and resetting episodes, observing camera feeds and robot state, and moving end effectors and grippers, including coordinating two arms. Supports LIBERO, RoboDojo, a simulator-free fake backend and remote backends over SSH or TCP, with configurable episode budgets, logs, live monitoring and frame-by-frame replay.
      7
      37 PyPI
      5
      Apache 2.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 39 tools

    Disambiguation3/5

    The set covers many distinct domains, but several closely related tools are easy to confuse: speak vs character_speak vs speak_on_echo, get_calendar_agenda vs show_calendar_agenda, and display/notification/card tools. Descriptions help clarify boundaries, but an agent still needs careful selection among similar speech, display, and notification actions.

    Naming Consistency4/5

    Most tools follow a predictable snake_case verb_noun or noun_action pattern, such as set_speaker_volume, list_reminders, and get_device_health. There are minor deviations like speak, character_speak, character_expression, and display_message/display_image, but the overall convention is readable and consistent.

    Tool Count2/5

    Thirty-nine tools is very large for a single assistant surface, spanning speech, display, camera, reminders, notifications, Spotify, calendar, focus, SwitchBot, and diagnostics. While many tools are meaningful, the volume creates a heavy selection burden and increases the chance of misselection.

    Completeness4/5

    Coverage is broad across most lifecycle areas: reminders can be created, listed, and cancelled; notifications can be published, listed, snoozed, dismissed, and configured; display, audio, camera, Spotify, calendar, focus, and SwitchBot operations are present. Minor gaps exist, such as no reminder edit/update and limited management for some captured media, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources