Sentinel Skill.

---
name: sentinel-iot
description: Operate Kajeet Sentinel cellular IoT fleets via the Kajeet MCP server (https://mcp.kajeet.dev/mcp). Use whenever the user mentions Kajeet, Sentinel, smartSIM, or asks to list devices, check cellular data usage, suspend or activate a SIM, inspect content filtering, or pull failover/GPS state on a managed IoT fleet.
---

# Sentinel IoT skill

This skill teaches the agent how to operate **Kajeet Sentinel** — a cellular IoT
fleet platform managing hundreds of thousands of SIMs across U.S. education,
transit, public sector, healthcare, and enterprise deployments. All operations
go through the **Kajeet IoT Connectivity MCP server**, which exposes Sentinel
as a typed, self-describing tool catalog.

## 1. Wire up the MCP server (one-time)

### 1a. Get an API key

Go to <https://kajeet.dev/api-keys> and create a key. A single key
authenticates REST, CLI, and MCP traffic — there is no separate "MCP key".

### 1b. Add the server to your host's MCP config

Pick **one** of the three auth patterns below. All three are accepted by
the server; the first is recommended.

**Option A — `Authorization: Bearer` header (recommended).** Most hosts
that support remote MCP servers accept a `headers` block:

```json
{
  "mcpServers": {
    "sentinel": {
      "url": "https://mcp.kajeet.dev/mcp",
      "transport": "streamable-http",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
```

If your host supports environment-variable expansion in the config (Claude
Code does, via `${VAR}` syntax), keep the secret out of the file:

```json
"headers": {
  "Authorization": "Bearer ${SENTINEL_API_KEY}"
}
```

…and then `export SENTINEL_API_KEY="..."` in your shell.