ChirpStack

Name: ChirpStack
Author: oliveres

by oliveresversion 0.1.1i★ –iRuns on your computer

Registry nameio.github.oliveres/chirpstack-mcp-server

Install

Overview

Description from the maker (original English)

Manage and live-debug LoRaWAN devices on a ChirpStack v4 network server over its gRPC API

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: CHIRPSTACK_SERVER, CHIRPSTACK_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: CHIRPSTACK_SERVER, CHIRPSTACK_API_KEY, CHIRPSTACK_TOOLSETS, CHIRPSTACK_TLS

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "chirpstack": {
      "command": "uvx",
      "args": [
        "chirpstack-mcp-server"
      ],
      "env": {
        "CHIRPSTACK_SERVER": "your-value",
        "CHIRPSTACK_API_KEY": "your-value",
        "CHIRPSTACK_TOOLSETS": "your-value",
        "CHIRPSTACK_TLS": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add chirpstack --env CHIRPSTACK_SERVER=your-value --env CHIRPSTACK_API_KEY=your-value --env CHIRPSTACK_TOOLSETS=your-value --env CHIRPSTACK_TLS=your-value -- uvx chirpstack-mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "chirpstack": {
      "command": "uvx",
      "args": [
        "chirpstack-mcp-server"
      ],
      "env": {
        "CHIRPSTACK_SERVER": "your-value",
        "CHIRPSTACK_API_KEY": "your-value",
        "CHIRPSTACK_TOOLSETS": "your-value",
        "CHIRPSTACK_TLS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "chirpstack": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "chirpstack-mcp-server"
      ],
      "env": {
        "CHIRPSTACK_SERVER": "your-value",
        "CHIRPSTACK_API_KEY": "your-value",
        "CHIRPSTACK_TOOLSETS": "your-value",
        "CHIRPSTACK_TLS": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

CHIRPSTACK_SERVER required env
host:port of the ChirpStack API (the web-UI port, usually 8080)
CHIRPSTACK_API_KEY secret required env
ChirpStack API key (tenant or global admin)
CHIRPSTACK_TOOLSETS env
Comma-separated toolsets to enable, or 'all' (default: devices,debug,applications,profiles,gateways)
CHIRPSTACK_TLS env
Use TLS instead of plain h2c (default: false)

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account oliveres, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32464 servers in this category
Published to the registry more recently than 31% of the other 32464 servers in this category
Basic checks equal to or better than 100% of the other 32464 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is ChirpStack safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: CHIRPSTACK_SERVER, CHIRPSTACK_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, yontu

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

yontu

by senrecep

Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

chirpstack-mcp-server

An MCP server for ChirpStack v4. It lets an AI agent (Claude Code, Claude Desktop, or any MCP client) manage a LoRaWAN network and — the part that matters while you are building a device application — debug devices live: queue a downlink, watch the uplinks and events as they arrive, iterate a payload codec, and inspect link quality, all from the coding session.

The server talks to ChirpStack's native gRPC API with a single API key. It carries no device- or vendor-specific logic.

*Real, unedited Claude Code session (2.5× speed, only the ChirpStack MCP tools): the agent reads the device profile's codec, spots the disconnected-probe sentinel in a raw uplink, deploys a fix with profile_set_codec, then waits for the device's next uplink with wait_for_event and confirms the decoded object.*

Install

uvx chirpstack-mcp-server        # run directly (needs uv: https://docs.astral.sh/uv/)

or

pip install chirpstack-mcp-server

Configure

Variable	Required	Default	Meaning
`CHIRPSTACK_SERVER`	yes	—	`host:port` of the ChirpStack API (the web-UI port, usually `8080`)
`CHIRPSTACK_API_KEY`	yes	—	API key from ChirpStack → API keys (tenant or global admin)
`CHIRPSTACK_TOOLSETS`	no	`devices, debug, applications, profiles, gateways`	comma-separated toolsets, or `all`
`CHIRPSTACK_TLS`	no	`false`	use TLS instead of plain HTTP/2
`CHIRPSTACK_TRANSPORT`	no	`stdio`	`stdio` or `streamable-http`
`CHIRPSTACK_HTTP_PORT`	no	`8000`	port for `streamable-http` (bound to `127.0.0.1`)

Claude Code

claude mcp add chirpstack -e CHIRPSTACK_SERVER=192.168.1.10:8080 -e CHIRPSTACK_API_KEY=eyJ... -- uvx chirpstack-mcp-server

Claude Desktop / generic MCP config

"mcpServers": { "chirpstack": { "command": "uvx", "args": ["chirpstack-mcp-server"], "env": { "CHIRPSTACK_SERVER": "192.168.1.10:8080", "CHIRPSTACK_API_KEY": "eyJ..." } } } }

Toolsets

Tools are grouped so an agent only sees what it needs. Names are _ .

Toolset	Default	Tools
`devices`	yes	list, get, create, update, delete, set_keys, activate, deactivate, flush_dev_nonces, enqueue, queue_get, queue_flush, metrics
`debug`	yes	`server_info`, `capture_start`, `capture_read`, `capture_stop`, `capture_list`, `wait_for_event`, `device_recent_events`
`applications`	yes	list, get, create, update, delete, list_device_tags
`profiles`	yes	list, get, create, update, delete, `profile_set_codec`, list_vendors, list_adr_algorithms
`gateways`	yes	list, get, create, update, delete, metrics
`multicast`	no	group CRUD, add/remove device, enqueue, queue_list, queue_flush
`fuota`	no	deployment CRUD, start, add/remove/list devices, list_jobs
`integrations`	no	`integration_list/get/set/delete` — one generic set for all ten ChirpStack integration kinds; `integration_get` redacts stored credentials unless `include_secrets=true`
`tenants`	no	tenant CRUD, tenant users, API keys
`relay`	no	relay devices and relay gateways

Enable more with CHIRPSTACK_TOOLSETS=devices,debug,profiles,multicast or CHIRPSTACK_TOOLSETS=all. server_info is the first call an agent should make to check the connection and the API key; its chirpstack_version/regions fields may come back null/empty since ChirpStack only serves those to a logged-in user session, never to an API key.

Live debugging

ChirpStack keeps the last ~10 events per device and streams new ones. The debug toolset turns that into something an agent can use between tool calls:

capture_start(target, kind) opens a background stream (events or frames for a device, gateway_frames for a gateway) into a 500-item ring buffer and returns a session_id.
device_enqueue(dev_eui, f_port, data_hex=...) queues the downlink.
capture_read(session_id, since_seq) returns everything that arrived since the last read — decoded uplinks (f_port, f_cnt, data_hex, codec object, per-gateway rssi/snr), ack/txack for the downlink, log entries when something went wrong.
capture_stop(session_id) when done. Idle sessions expire after 30 minutes.

For quick looks: wait_for_event(dev_eui, timeout_s) blocks up to 60 s for the next live event — it only returns events newer than the moment it was called, never the history ChirpStack replays; device_recent_events(dev_eui) returns that history without keeping a session.

Class A devices only receive a downlink after their next uplink; Class C devices get it right away.

Security notes

The API key is read from the environment and never appears in tool output. device_get hides root keys unless asked with include_keys=true.
device_get/multicast_get hide session keys unless include_keys=true.
integration_get redacts stored credentials unless include_secrets=true.
is reserved: integration_set/multicast_update keep the stored value wherever it appears (so an edited _get result can be handed straight back), and integration_set/multicast_create refuse it when there is nothing to keep.
Plain HTTP/2 (h2c) is the default because ChirpStack's API port is plain by default. Plain h2c sends the API key as a cleartext bearer token on the wire; use it only on a trusted LAN, and set CHIRPSTACK_TLS=true (behind a TLS-terminating proxy that speaks gRPC) or a VPN elsewhere.
streamable-http has no authentication of its own and binds to 127.0.0.1. Do not expose it on a public interface.
The HTTP transport validates Host/Origin headers (DNS-rebinding protection), so a web page in the operator's browser cannot open an MCP session against the loopback listener.
Destructive tools are annotated (destructiveHint) so MCP clients can ask before running them.
Enabling the tenants toolset lets the agent mint API keys; api_key_create returns the new token once, in its result.

Development

uv sync

uv run pytest # unit tests uv run ruff check . && uv run pyright tests/integration/up.sh # throwaway ChirpStack in Docker + API key set -a; . .integration/env; set +a uv run pytest -m integration tests/integration/down.sh

Design notes live in docs/design.md.

ChirpStack

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

yontu

README from the maker

chirpstack-mcp-server

Install

or

Configure

Claude Code

Claude Desktop / generic MCP config

Toolsets

Live debugging

Security notes

Development

License