ossm

The OSSM WebSocket Control MCP Server exposes a set of functions that let an AI-driven controller interact with OSSM devices using binary WebSocket commands. It supports smooth, timed motion through ossm_smooth_move, continuous loop patterns via ossm_loop, and localized vibration patterns with ossm_vibrate. Global safety controls such as ossm_set_speed_limit, ossm_set_acceleration, and ossm_set_range_limit help keep motion within safe hardware bounds, while ossm_pause acts as an emergency stop from any control source. This server is designed to integrate into an MCP-enabled environment, allowing you to script complex motion sequences or dynamic responses to events within your AI workflows.

Prerequisites:\n- OSSM device with compatible firmware\n- Godot WebSocket bridge application running on port 8081\n- MCP-compatible AI\n\nSteps:\n1) Install dependencies in the ossm-mcp-server directory:\nbash\nnpm install\n\n2) Add to MCP configuration (example: claude_desktop_config.json):\njson\n{\n "mcpServers": {\n "ossm-websocket-control": {\n "command": "node",\n "args": ["/absolute/path/to/ossm-mcp-server.js"]\n }\n }\n}\n\n3) Restart the AI desktop application to load the new MCP server.\n4) Ensure the Godot WebSocket bridge and OSSM device are reachable at the configured endpoints (e.g., port 8081).

Tips and notes:\n- Range limits affect loop commands automatically, but vibrate commands require re-sending after changing global settings.\n- Safety: Global speed and acceleration limits apply across all motion modes; use ossm_pause for immediate halts if anomalies are detected.\n- Vibrate commands operate with self-contained position and range parameters; if you adjust global range or speed limits, re-send a vibrate command to apply the new settings.\n- For localized effects with high frequency, use smaller ranges; for full-rail patterns, rely on the global range limits to constrain motion.\n- The OSSM server expects a properly configured MCP environment; ensure the MCP client can access the ossm-websocket-control server endpoint.\n- Test sequences incrementally, watching for timing drift or hardware strain during motion.