Mbotmcp

Created By
deemkeena year ago
Overview

what is MbotMcp?

MbotMcp is a project that demonstrates how to control an mBot2 robot using Spring AI and Model Context Protocol (MCP), allowing users to issue natural language commands to control the robot.

how to use MbotMcp?

To use MbotMcp, set up the MQTT broker, configure the Spring Boot application, upload the Python script to the mBot2, and then issue commands through an AI client that supports MCP.

key features of MbotMcp?

  • Control mBot2 robot using natural language commands.
  • Integration with AI models for autonomous control.
  • Simple setup with Docker for MQTT broker.

use cases of MbotMcp?

  1. Educational robotics projects for learning programming and AI.
  2. Home automation tasks using the mBot2 robot.
  3. Research in human-robot interaction using natural language processing.

FAQ from MbotMcp?

  • What is required to run MbotMcp?

You need Java 21, Maven, an mBot2 robot, and an MQTT broker.

  • Can I use MbotMcp without an MQTT broker?

Yes, but the MQTT broker is recommended for message passing between the application and the robot.

  • How can I issue commands to the robot?

You can issue commands through an AI client that supports the Model Context Protocol.

Server Config

{
  "mcpServers": {
    "mbotmcp": {
      "command": "path-to-java-executable",
      "args": [
        "-jar",
        "/path-to-repo/mbotmcp/target/mbotmcp-0.0.1-SNAPSHOT.jar"
      ],
      "env": {
        "MQTT_USERNAME": "<mqtt server username>",
        "MQTT_PASSWORD": "<mqtt server password>",
        "MQTT_SERVER_URI": "mqtt server url"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
deemkeen
Star
-
Language
-
License
-

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago