DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to command a robot from a Claude chat window with Quackd

Send a goal to one of your registered robots from Claude over MCP.

Authorization notice. Quackd is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. Connecting Claude to Quackd uses your model API key and gives chat access to command your robots, so restrict who can reach that session.

Who it is forA robot owner who prefers chatting with Claude to typing terminal commands.

The problemSwitching to a terminal for every goal interrupts the flow of asking a robot to do something.

The outcomeYou state a goal in chat and the registered robot runs it, with Quackd enforcing its skill and step limits.

What you need first

  • Python installed on a laptop or computer
  • An API key for one hosted model (Claude, OpenAI, Gemini, Grok and others), or a local model served by Ollama, vLLM, llama.cpp or LM Studio
  • For the simulated duck: the quackd[microduck] extra
  • For real hardware: a supported robot such as the SO-101 arm over LeRobot, plus its serial or USB connection

Steps

  1. Install Quackd and register your robot by name following the README (inferred, check the README)
  2. Connect Quackd to Claude through the MCP setup described in the README (inferred, check the README)
  3. State a goal in the Claude chat, naming the robot
  4. Check the reply for the outcome and any request for your approval

Prompt for your agent

Using the rokbenko/quackd repo, set up the MCP connection so Claude can reach quackd, then send the goal "Find the ball and kick it" to a robot registered as <robot-name>. Report what Claude returned and the final status. Verify that quackd applied the robot's skill list and step limit to the run.

Caveat. The README describes chat as a way to state goals, but the exact MCP setup steps are not in the truncated text, so follow the MCP section of the README for them.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page