# ChirpStack LoRaWAN MCP

> ChirpStack LoRaWAN MCP is a paid API for AI agents from api.m2mcent.com, paid per call via x402, $0.18/call, status unknown (last checked 2026-09-15).

Processes LoRaWAN IoT device data and network management commands via ChirpStack through a managed API endpoint

## Facts

- Endpoint: POST https://api.m2mcent.com/chirpstack-lorawan-mcp/api/process
- Price: $0.18/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/chirpstack-lorawan-mcp-d6c56fde
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hjufy_hWoETUJV8iABSEm

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability chirpstack-lorawan-mcp-d6c56fde -d '<json body>'
```

Example prompt: Can you query my ChirpStack LoRaWAN network server to get the latest uplink data from my temperature sensor device with EUI 0004A30B001C0530?

## When to prefer this

Choose this endpoint when you need to interact with a ChirpStack-managed LoRaWAN network server from an AI agent — particularly for querying device uplinks, sending downlinks, managing device registrations, or automating IoT workflows without standing up your own ChirpStack infrastructure.

## Known failure modes

- Invalid or malformed data payload returns an error response
- Device EUI not found on the network server returns a 404-equivalent error
- Authentication or permission issues result in access denied
- Gateway offline causes timeout or no-data response
- Malformed LoRaWAN command syntax causes processing failure

## How this service works

The premier global index of 1,069 monetized MCP nodes across 205 specialized subdomains. Gasless USDC runtime settlements via x402 V2 Spec on Base L2. Save 95% token context.

## Output

Returns a response from the ChirpStack LoRaWAN network server, which may include device uplink payloads, device metadata, gateway statistics, downlink acknowledgements, or network configuration results depending on the command issued.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "payload": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "success": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/chirpstack-lorawan-mcp-d6c56fde/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.m2mcent.com](https://www.zero.xyz/host/api.m2mcent.com/llms.txt)