Azure IoT Hub MCP Server

Created By
tlaukkanena year ago
MCP Server for Azure IoT Hub mainly for read-only monitoring purposes. Uses Azure CLI for authentication.
Overview

what is azure-iothub-mcp-server?

The azure-iothub-mcp-server is a monitoring server designed for Azure IoT Hub, primarily focused on read-only monitoring functionalities. It utilizes Azure CLI for authentication, making it easy to integrate with existing Azure services.

how to use azure-iothub-mcp-server?

To use the azure-iothub-mcp-server, clone the repository from GitHub, set up your Azure IoT Hub, and authenticate using Azure CLI. Once set up, you can monitor your IoT devices in a read-only mode.

key features of azure-iothub-mcp-server?

  • Read-only monitoring of Azure IoT Hub data
  • Utilizes Azure CLI for secure authentication
  • Easy integration with existing Azure services

use cases of azure-iothub-mcp-server?

  1. Monitoring device telemetry data in real-time.
  2. Tracking device status and health without making changes to the device configurations.
  3. Generating reports based on the monitored data for analysis.

FAQ from azure-iothub-mcp-server?

  • Can I modify device settings using this server?

No, the azure-iothub-mcp-server is designed for read-only access, so it cannot modify device settings.

  • Is there any cost associated with using this server?

The server itself is free to use, but you may incur costs based on your Azure IoT Hub usage.

  • What programming language is used in this project?

The project is developed in TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tlaukkanen
Star
0
Language
TypeScript
License
MIT license
Category
monitoring
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago