robot-mcp-server

Created By
showkeyjara year ago
mcp server for robot and automations
Overview

What is robot-mcp-server?

robot-mcp-server is a server designed to provide robot control capabilities for large language models, enabling automation and control of various robotic systems.

How to use robot-mcp-server?

To use robot-mcp-server, set up a Python environment, install the necessary dependencies, and connect to the MCP service to control robots and drones.

Key features of robot-mcp-server?

  • Supports motion control for Unitree robots.
  • Enables takeoff and landing control for DJI drones.
  • Standard interface based on Model Context Protocol (MCP).
  • Real-time status monitoring.
  • Emergency stop mechanism.
  • Comprehensive logging capabilities.

Use cases of robot-mcp-server?

  1. Controlling robotic movements for research and development.
  2. Automating drone operations for aerial photography or surveillance.
  3. Integrating with AI models for enhanced robotic functionalities.

FAQ from robot-mcp-server?

  • What programming language is required?

Python 3.10 or higher is required to run the server.

  • Can I control multiple robots at once?

Yes, the server can manage multiple robot connections simultaneously.

  • Is there a license for this project?

Yes, the project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
showkeyjar
Star
2
Language
Python
License
MIT license

Recommend Servers

View All
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.

8 hours ago