nodrix MCP server
Commit 12 Nov 2026Memungkinkan asisten AI untuk membaca telemetri IoT dan mengontrol hardware seperti ESP32 atau Arduino melalui platform berbasis Cloudflare yang di-host sendiri.
Juga dikenal sebagai decoded-cipher/nodrix
- Stars
- 46
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- 1.0.1
- Commit terakhir
- 12 Nov 2026
- Lisensi
- MIT
Apa itu nodrix MCP?
nodrix adalah MCP server. Memungkinkan asisten AI untuk membaca telemetri IoT dan mengontrol hardware seperti ESP32 atau Arduino melalui platform berbasis Cloudflare yang di-host sendiri.
Ringkasan dibuat dari README proyek
Tentang nodrix MCP server
nodrix menyediakan platform IoT self-hosted yang berjalan sepenuhnya di dalam akun Cloudflare Anda sendiri menggunakan Workers, Durable Objects, D1, dan R2. Platform ini memungkinkan hardware seperti Arduino atau ESP32 untuk mengirim telemetri via HTTPS atau WebSockets tanpa memerlukan skema yang ditentukan sebelumnya atau broker MQTT terkelola. Setelah data masuk, variabel akan dibuat secara otomatis, dan Anda dapat melihatnya melalui dashboard drag-and-drop real-time atau melalui read API yang bersih.
Native MCP server memungkinkan asisten AI untuk berinteraksi dengan hardware Anda secara remote. Karena perangkat terhubung ke deployment Cloudflare Anda dan bukan ke mesin lokal, hardware dapat berada di mana saja. Pengguna dapat mengaktifkan akses read-only atau kontrol penuh dengan mengubah pengaturan spesifik di dashboard. Sistem ini menyertakan 12 read tools untuk memeriksa project, variabel, dan otomasi, serta 16 write tools untuk mengelola konfigurasi dan mengontrol hardware melalui perintah seperti set_variable.
Keamanan dikelola melalui izin berbasis owner dan project tokens. Platform ini mendukung multi-user roles termasuk owner, admin, dan member, lengkap dengan audit log untuk melacak tindakan istimewa. Untuk mencegah kehilangan data yang tidak disengaja, toolset ini dirancang tanpa adanya delete tools.
Apa yang bisa Anda lakukan dengannya
- 1Monitor data sensor jarak jauhMinta asisten AI untuk mengambil pembacaan suhu dan kelembapan saat ini dari project IoT tertentu.
- 2Kontrol komponen hardwareInstruksikan AI untuk menyalakan relay atau menyesuaikan pengaturan dengan mengirimkan perintah ke hardware.
- 3Kelola konfigurasi IoTGunakan client AI untuk membuat project, dashboard, atau aturan otomasi baru di dalam infrastruktur Anda.
- 4Analisis telemetri historisMinta laporan time-series dari perubahan variabel untuk memahami perilaku perangkat dari waktu ke waktu.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal nodrix MCP
Format diverifikasi 10 Nov 2026Instal nodrix MCP di Claude Code
$ claude mcp add --transport http nodrix https://{host}/v1/mcp/oauthInstal nodrix MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"nodrix": {
"url": "https://{host}/v1/mcp/oauth"
}
}
}Instal nodrix MCP di VS Code
.vscode/mcp.json
{
"servers": {
"nodrix": {
"type": "http",
"url": "https://{host}/v1/mcp/oauth"
}
}
}Instal nodrix MCP di Codex
~/.codex/config.toml
[mcp_servers.nodrix]
url = "https://{host}/v1/mcp/oauth"Instal nodrix MCP di Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"nodrix": {
"httpUrl": "https://{host}/v1/mcp/oauth"
}
}
}Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Belum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks
- Source repository terhubung dan dapat dijangkaudecoded-cipher/nodrix is public and reachablegithub.com/decoded-cipher/nodrix ↗Lolos
- Paket menyebut repo ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-11-12github.com/decoded-cipher/nodrix ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis di paket maupun dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote menjawab handshake MCPEndpoint did not answer initialize: unreachableTemuan
README
Lihat di GitHubnodrix
The IoT platform Cloudflare didn't build. Point your hardware at one endpoint over HTTPS or WebSocket, watch variables appear on their own, build realtime drag-and-drop dashboards, automate, and read it all back through a clean API — entirely on infrastructure you own. nodrix is single-tenant and open source: it deploys into your Cloudflare account on Workers, Durable Objects, D1, and R2.
Features
- 📡 Telemetry over HTTPS or WebSocket — hardware POSTs JSON to a project; variables auto-create on first sight. No schema to define, no MQTT broker to run.
- 📊 Realtime dashboards — a drag-and-drop widget grid streams updates over hibernating WebSockets; share any dashboard read-only by public link.
- 🧩 Embeddable widgets — every widget is a framework-agnostic Web Component you can lift straight into your own app.
- 🎮 Two-way control — toggles, sliders, color pickers, and buttons write values back to hardware via short polls or a control socket.
- 🤖 Visual automations — variable, schedule, sunrise/sunset, and event triggers run conditions and actions: webhooks, code snippets, and service integrations.
- 🔌 Integrations — fan out to HTTP, email, and chat (Slack, Telegram, Discord, and more).
- 📖 Clean read API — latest state, time-series, and variable listings behind one token.
- 🧠 Native MCP server — read telemetry and control hardware from an AI assistant, on devices you are not physically next to. Owner-gated and off by default; see AI assistants (MCP).
- 👥 Multi-user — owner / admin / member roles, email invites, and social sign-in (Google, GitHub).
- 📝 Audit log — every privileged action recorded and paginated in the UI.
Quick start
-
Deploy to your Cloudflare account — one click, or
bun run deploy:platformfrom a clone. -
Create the owner account — the first visit prompts a "Create owner account" page; the first signup becomes
owner. -
Create a project and mint a project token from the dashboard.
-
Send telemetry — variables are created the moment data arrives:
curl -X POST https://<your-worker>/v1/telemetry \ -H "Authorization: Bearer $NODRIX_TOKEN" \ -H "Content-Type: application/json" \ -d '{"metrics":{"temperature":23.4,"humidity":61}}' -
Read it back:
curl https://<your-worker>/v1/projects/<project>/state \ -H "Authorization: Bearer $NODRIX_TOKEN"
AI assistants (MCP)
nodrix ships a native Model Context Protocol server, so an assistant can read a project's telemetry and — once you allow it — act on the hardware. Because devices report to your deployment rather than to your laptop, the board does not need to be plugged into the machine running the assistant; it can be in another building.
Two endpoints, both Streamable HTTP:
| Endpoint | Auth | For |
|---|---|---|
/v1/mcp |
Bearer token | CLI and IDE clients |
/v1/mcp/oauth |
OAuth | claude.ai-style connectors |
Both are off by default. The owner flips them in Settings → More:
mcp_enabled— the master switch. While it is off,/v1/mcpreturns 404, so a disabled server looks absent rather than merely forbidden.mcp_write_enabled— gates the management and control tools. Until it is on, even an admin-scope token gets read-only tools, so an assistant cannot command hardware by default.
12 read tools — list_projects, list_variables, get_state, get_series, list_dashboards, get_dashboard, list_widget_types, list_widgets, list_block_types, list_integration_kinds, list_automations, list_integrations.
16 write tools — creating and updating projects, variables, dashboards, widgets, automations, and integrations, plus set_variable (how an assistant turns a relay on), run_automation, emit_event, and test_integration.
There are no delete tools, by design. Every tool resolves its target project through the token's scope before it runs, so it cannot reach a project the token cannot.
Architecture
- Worker (worker/) — a single Hono app. Durable Objects for Project, Dashboard, Scheduler, and the MCP agent; one Workflow for provisioning; D1 (metadata), R2 (telemetry history), KV (read cache + JWKS).
- Web (web/) — Vue 3 + Tailwind + Reka UI admin panel and drag-and-drop dashboard builder, built and served as Worker static assets.
- Shared (shared/) — framework-agnostic Web Component widgets, the integration catalog, and automation blocks, consumed by both web and worker so there is a single source of truth.
- Deploy (deploy/) — the small config carrier behind the one-click Deploy to Cloudflare.
worker/ Cloudflare Worker — API, Durable Objects, Workflow
web/ Vue 3 admin panel + dashboard builder
shared/ Web Component widgets, integration catalog, automation blocks
deploy/ One-click Deploy to Cloudflare config
scripts/ Build, version, and migration generators
Storage
| Store | Holds |
|---|---|
| Project DO (SQLite) | Latest variable state, recent ring buffer, pending control writes, flush cursor |
| R2 | Cold telemetry history (NDJSON, partitioned by project + hour) |
| D1 | Users, sessions, accounts, projects, variables, dashboards, tokens, automations, integrations, audit log, OAuth provider config (metadata only — never any telemetry point) |
| KV | Cached /state responses and JWKS |
| Dashboard DO | Per-dashboard subscriptions + hibernated WebSockets |
| Scheduler DO | One alarm at the next schedule/sunset automation fire time |
Authentication
Better Auth handles sign-in. Email + password is on by default; Google and GitHub OAuth can be enabled at runtime from Settings → Sign-in providers (the owner enters a client ID + secret per provider, and the login page shows the matching buttons immediately).
The first signup on a fresh deployment becomes owner. After that, registration is closed: the owner invites people from Users, each with an owner / admin / member role. Sessions are cookie-based and persist 30 days; each device is a separate session, listed and revokable from Users.
Development
nodrix uses Bun.
bun install
bun run dev # worker (wrangler dev)
bun run dev:web # web (vite)
bun run typecheck
bun run build
bun run deploy:platform # build + deploy the worker
Links
- Site — https://nodrix.live
- Changelog — https://nodrix.live/changelog
- Roadmap — https://nodrix.live/roadmap
License
MIT © Arjun Krishna
Pertanyaan tentang nodrix MCP
Bagaimana cara menambahkan nodrix MCP ke Claude Code?
Jalankan claude mcp add --transport http nodrix https://{host}/v1/mcp/oauth di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan nodrix MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Bisakah asisten AI mengontrol hardware saya?
Ya, setelah Anda mengaktifkan write tools di pengaturan, asisten dapat menggunakan tools seperti set_variable untuk memberikan perintah ke hardware.
Apakah hardware saya harus terhubung ke komputer agar AI dapat bekerja?
Tidak, karena perangkat mengirimkan data ke deployment Anda dan bukan ke mesin lokal, hardware dapat berada di lokasi yang berbeda.
Apakah MCP server aktif secara default?
Tidak, MCP server nonaktif secara default dan harus diaktifkan oleh pemilik melalui pengaturan.