Log inSubmit server
ChirpStack logo

ChirpStack

Manage ChirpStack v4 LoRaWAN devices, applications, profiles, gateways, and live device debugging through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install ChirpStack

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "chirpstack": {
      "command": "uvx",
      "args": [
        "chirpstack-mcp-server"
      ],
      "env": {
        "CHIRPSTACK_SERVER": "YOUR_VALUE_HERE",
        "CHIRPSTACK_API_KEY": "YOUR_VALUE_HERE",
        "CHIRPSTACK_TOOLSETS": "YOUR_VALUE_HERE",
        "CHIRPSTACK_TLS": "YOUR_VALUE_HERE",
        "CHIRPSTACK_TRANSPORT": "YOUR_VALUE_HERE",
        "CHIRPSTACK_HTTP_PORT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

uvx chirpstack-mcp-server

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 12d ago.

Overview

The ChirpStack MCP server connects AI agents to a ChirpStack v4 network server through its native gRPC API. It supports device administration, downlink queuing, event capture, payload codec updates, application and gateway management, and inspection of link metrics. Use it when developing or operating LoRaWAN devices and you want an agent to query the network or verify behavior against live uplinks. Access is configured with one ChirpStack API key and selectable toolsets.

Use cases

  • Debug live LoRaWAN uplinks and downlinks
  • Manage ChirpStack device registrations and keys
  • Iterate device-profile payload codecs
  • Inspect gateway metrics and link quality
  • Operate multicast and FUOTA resources

Key features

  • ChirpStack v4 gRPC API access
  • Device, application, profile, and gateway management
  • Live event capture and downlink debugging
  • Payload codec updates
  • Configurable MCP toolsets
  • stdio and streamable HTTP transports

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

4/4 checks healthy over the last 36d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · chirpstack-mcp-server (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How ChirpStack works

What the ChirpStack MCP server does

The ChirpStack MCP server exposes ChirpStack v4 operations through the Model Context Protocol. It is intended for LoRaWAN network administration and for live debugging during device application development. The server does not add device- or vendor-specific logic; it forwards supported operations to ChirpStack's native gRPC API.

The default toolsets cover devices, debugging, applications, device profiles, and gateways. Optional toolsets add multicast groups, FUOTA deployments, integrations, tenants, and relay resources. Tool visibility can be limited so an agent receives only the operations relevant to a task.

How it works

The ChirpStack MCP server authenticates to the ChirpStack API with an API key read from the environment. Its default transport is stdio, and it can also serve MCP over streamable HTTP on a loopback port. TLS can be enabled for the connection to ChirpStack.

For live diagnostics, an agent can start a capture for a device or gateway. Device captures use a background stream and a ring buffer, allowing the agent to read new events between tool calls. Captured data can include decoded uplinks, frame counters, payload bytes, codec output, per-gateway RSSI and SNR, downlink acknowledgements, and log entries. A shorter workflow can wait for the next event or retrieve recent device history.

Class A devices receive queued downlinks after their next uplink, while Class C devices can receive them immediately. Capture sessions expire after 30 minutes when idle.

Setup and configuration

Install the package with uvx chirpstack-mcp-server or install it with pip. Set these required variables:

  • CHIRPSTACK_SERVER: the ChirpStack API host and port, commonly the web UI port such as 8080.
  • CHIRPSTACK_API_KEY: a tenant or global administrator API key created in ChirpStack.

Optional settings select toolsets, enable TLS, choose stdio or streamable-http, and set the HTTP port. The default toolsets are devices, debug, applications, profiles, gateways; use all or a comma-separated list to enable additional groups.

Claude Code can register the server with its MCP command-line configuration. Claude Desktop and other MCP clients can use a standard server entry with the executable and environment variables.

Tools and capabilities

The ChirpStack MCP server includes tools for:

  • Listing, reading, creating, updating, and deleting devices, applications, profiles, and gateways.
  • Setting device keys, activating or deactivating devices, flushing nonces, queuing downlinks, and viewing device metrics.
  • Starting, reading, listing, and stopping captures, waiting for events, and inspecting recent device events.
  • Updating a profile's codec and listing profile vendors or ADR algorithms.
  • Managing multicast groups, FUOTA deployments, integrations, tenants, tenant users, API keys, relay devices, and relay gateways when those toolsets are enabled.

The server_info tool is intended as an initial connection and credential check. ChirpStack may return empty version or region fields for API-key requests because those values are served only to logged-in user sessions.

Limitations and notes

Plain HTTP/2 is the default and sends the API key as a cleartext bearer token, so it should be limited to a trusted LAN. Use TLS behind a suitable gRPC-speaking proxy or use a VPN for other network locations. The streamable HTTP listener has no separate authentication and binds to 127.0.0.1; it should not be exposed publicly.

Sensitive values receive special handling. API keys do not appear in tool output, device and session keys are hidden unless explicitly requested, and integration credentials are redacted by default. Tenant administration can create API keys, and the newly created token is returned once. Destructive operations are annotated so compatible MCP clients can request confirmation.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about ChirpStack

ChirpStack is an MCP server that connects AI agents to a ChirpStack v4 LoRaWAN network server through its native gRPC API. Its main tools manage devices, applications, profiles, gateways, downlinks, and live event captures for debugging uplinks, payload codecs, and link quality.

Install it with `uvx chirpstack-mcp-server` or `pip install chirpstack-mcp-server`. Running with uv requires uv to be installed. Configure the required server address and API key as environment variables before adding it to an MCP client.

Set `CHIRPSTACK_SERVER` to the ChirpStack API host and port and `CHIRPSTACK_API_KEY` to a tenant or global administrator key. Optionally set toolsets, TLS, transport, and the streamable HTTP port.

Yes, ChirpStack works with Claude Code and Claude Desktop through their MCP configuration. Claude Code can register it with `claude mcp add`, while Claude Desktop uses a standard `mcpServers` entry with the command and required environment variables.

Related MCP servers

All in Industrial & IoT All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewChirpStack AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/chirpstack?style=directory)](https://allmcps.com/mcp/chirpstack)
HTML Embed
<a href="https://allmcps.com/mcp/chirpstack"><img src="https://allmcps.com/api/badge/chirpstack?style=directory" alt="ChirpStack on AllMCPs" /></a>