Developer · Local MCP server
ChirpStack
Manage and live-debug LoRaWAN devices on a ChirpStack v4 network server over its gRPC API.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.oliveres/chirpstack-mcp-server- Version
- 0.1.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-08-30
- Updated
- 2026-08-30
- Publisher
- oliveres (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/oliveres) · how
- Repository
- github.com/oliveres/chirpstack-mcp-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | chirpstack-mcp-server | 0.1.1 | stdio |
How to connect ChirpStack
ChirpStack runs locally from a Python package published to PyPI: chirpstack-mcp-server version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx chirpstack-mcp-server. It reads these environment variables: CHIRPSTACK_SERVER (required), CHIRPSTACK_API_KEY (required, secret), CHIRPSTACK_TOOLSETS and CHIRPSTACK_TLS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"chirpstack-mcp-server": {
"command": "uvx",
"args": [
"chirpstack-mcp-server"
],
"env": {
"CHIRPSTACK_SERVER": "<value>",
"CHIRPSTACK_API_KEY": "<secret>",
"CHIRPSTACK_TOOLSETS": "<value>",
"CHIRPSTACK_TLS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| ChecktrailLocal code validation with explicit execution trust and evidence of what actually ran. | Local · stdio |
| ChimeraForgeLocal-first LLM deployment planner: GPU/VRAM sizing, cost and latency, with provenance. | Local · stdio |
| ChippBuild and manage Chipp AI apps: prompts, knowledge, custom actions, and chat with your apps. | Remote · HTTPLive check: sign-in required |
| ChipzenAI poker arena for agents. Play rated poker on chipzen.ai against LLM bots and human-built bots. | Local · stdio |
| ChromaDB Remote MCP ServerRemote ChromaDB vector database MCP server with streamable HTTP transport. | Remote & Local · HTTPLive check: ✗ no handshake |
| Chrome Debugger MCPChrome breakpoint debugging MCP server for inspecting runtime values and stepping through code. | Local · stdio |
| Chromedevtoolsmcp MCPA paid remote MCP for AI agent browser DevTools MCP, built to return verdicts, receipts, usage logs,. | Remote · HTTPLive check: ✗ no handshake |
| Chromium BridgeMCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code: browser automation. | Local · stdio |