Nwo Robotics

Created By
RedCiprianPater2 months ago
Control real robots and IoT devices through AI agents. Self-register with wallet authentication, pay with ETH for tier upgrades, and execute Vision-Language-Action commands. Features robot control, sensor monitoring, multi-agent coordination, and autonomous payments.
Overview

NWO Robotics MCP Server

MCP Version License

A Model Context Protocol (MCP) server for the NWO Robotics API. Enables AI agents (Claude, Cursor, etc.) to discover and control real robots through a standardized tool interface.

What is MCP?

The Model Context Protocol (MCP) is an open standard by Anthropic that allows AI assistants to discover and use tools dynamically. This server exposes NWO Robotics capabilities as MCP tools that any MCP-compatible agent can use.

Features

  • 🤖 Robot Control - Send VLA (Vision-Language-Action) commands to robots
  • 📡 IoT Monitoring - Query sensors and control actuators
  • 🔑 Self-Registration - Agents can register and get API keys
  • 💎 Autonomous Payment - Pay with ETH for tier upgrades
  • 👥 Multi-Agent Support - Join coordinated agent swarms
  • 📊 Real-time Telemetry - Monitor robot status and sensor data

Installation

npm install -g @nwo-capital/mcp-server-robotics

Option 2: Docker

docker pull nwocapital/mcp-server-robotics

Option 3: Direct from GitHub

npx -y @nwo-capital/mcp-server-robotics

Configuration

Step 1: Get API Credentials

Register as an AI agent at https://nwo.capital/webapp/agent.md or use the self-registration tool.

Step 2: Configure MCP Client

Add to your Claude Desktop, Cursor, or other MCP client:

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "nwo-robotics": {
      "command": "npx",
      "args": ["-y", "@nwo-capital/mcp-server-robotics"],
      "env": {
        "NWO_API_KEY": "your_api_key_here",
        "NWO_AGENT_ID": "your_agent_id_here"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "nwo-robotics": {
      "command": "npx",
      "args": ["-y", "@nwo-capital/mcp-server-robotics"],
      "env": {
        "NWO_API_KEY": "your_api_key_here",
        "NWO_AGENT_ID": "your_agent_id_here"
      }
    }
  }
}

Docker:

{
  "mcpServers": {
    "nwo-robotics": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e", "NWO_API_KEY",
        "-e", "NWO_AGENT_ID",
        "nwocapital/mcp-server-robotics"
      ],
      "env": {
        "NWO_API_KEY": "your_api_key_here",
        "NWO_AGENT_ID": "your_agent_id_here"
      }
    }
  }
}

Available Tools

Robot Control

ToolDescription
get_robot_statusGet status of all connected robots
execute_robot_taskSend VLA command to a robot
move_robotNavigate robot to coordinates
stop_robotEmergency stop a robot
get_robot_telemetryReal-time sensor data from robot

IoT & Sensors

ToolDescription
query_sensorsQuery IoT sensors by location
get_sensor_dataGet data from specific sensor
control_actuatorControl motors, servos, etc.

Agent Management

ToolDescription
register_agentSelf-register as new AI agent
check_balanceCheck API quota and usage
upgrade_tierPay with ETH for tier upgrade
get_agent_profileGet agent account info

Multi-Agent

ToolDescription
list_agentsList agents in swarm
coordinate_taskCoordinate multi-agent task
share_resourceShare robot with other agents

Usage Examples

Example 1: Control a Robot

User: "Move robot_001 to the loading dock"

Claude uses: execute_robot_task
{
  "robot_id": "robot_001",
  "instruction": "Move to loading dock",
  "coordinates": {"x": 50, "y": 100}
}

Example 2: Query Sensors

User: "What's the temperature in warehouse 3?"

Claude uses: query_sensors
{
  "location": "warehouse_3",
  "sensor_type": "temperature"
}

Example 3: Check API Usage

User: "How many API calls do I have left?"

Claude uses: check_balance
{} → Returns quota remaining

Environment Variables

VariableRequiredDescription
NWO_API_KEYYesYour API key from registration
NWO_AGENT_IDYesYour agent ID
NWO_API_BASENoAPI base URL (default: https://nwo.capital/webapp)

Self-Registration

Don't have API credentials? The server includes a tool to self-register:

User: "Register me as a new agent with wallet 0x123..."

Claude uses: register_agent
{
  "wallet_address": "0x123...",
  "agent_name": "MyAgent",
  "capabilities": ["vision", "navigation"]
}

API Pricing

TierPriceAPI Calls
Free0 ETH100,000/month
Prototype0.015 ETH/month500,000/month
Production0.062 ETH/monthUnlimited

Support

License

MIT-0 - No Attribution Required

Contributing

Contributions welcome! See CONTRIBUTING.md

Server Config

{
  "mcpServers": {
    "nwo-robotics": {
      "command": "npx",
      "args": [
        "-y",
        "@nwo-capital/mcp-server-robotics"
      ],
      "env": {
        "NWO_API_KEY": "<YOUR_API_KEY>",
        "NWO_AGENT_ID": "<YOUR_AGENT_ID>"
      }
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
RedCiprianPater
Star
-
Language
-
License
-
Category

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