Modbus Mcp

Created By
ezhuka year ago
A Model Context Protocol (MCP) server for Modbus.
Overview

what is Modbus MCP?

Modbus MCP is a lightweight Model Context Protocol (MCP) server that connects LLM agents to Modbus devices, enabling secure integration of AI-driven workflows with Building Automation and Industrial Control systems.

how to use Modbus MCP?

To use Modbus MCP, install the uv dependency manager, clone the repository, install project dependencies, and run the server using the command uv run modbus-mcp. You can then connect to the server using the MCP Inspector.

key features of Modbus MCP?

  • Seamless integration with Modbus devices
  • Real-time monitoring of sensor data
  • Ability to actuate devices and orchestrate automation tasks
  • Supports read and write operations on Modbus registers

use cases of Modbus MCP?

  1. Monitoring real-time data from industrial sensors.
  2. Automating control tasks in building management systems.
  3. Integrating AI agents for enhanced decision-making in industrial applications.

FAQ from Modbus MCP?

  • What is the purpose of Modbus MCP?

Modbus MCP serves as a bridge between AI agents and Modbus devices, facilitating automation and data exchange.

  • Is Modbus MCP free to use?

Yes! Modbus MCP is open-source and free to use.

  • How can I deploy Modbus MCP?

You can deploy Modbus MCP as a Docker container or run it directly on your machine.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ezhuk
Star
0
Language
Python
License
MIT 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