Offline Protocol CLI and MCP server

Install

npm install -g @offline-protocol/cli
offline --version

npx -y @offline-protocol/cli --version

Changes in 0.3.3

• offline create, offline add and the MCP tools resolve SDK 0.33.0, so new scaffolds install @offline-protocol/mesh-sdk 0.33.0, and the registry covers requestMeshPermissions, the development warnings and 0.33.0 mesh delivery. Hosted MCP serves it too.
• offline init and new scaffolds start the local MCP server with @offline-protocol/cli@0.3.3.

Changes in 0.3.2

• offline create, offline add and the MCP tools resolve SDK 0.32.0, so scaffolds install @offline-protocol/mesh-sdk 0.32.0. The registry covers service subscriptions, adds the C# binding (offline-protocol-csharp, a preview from the SDK repository) and the Bluetooth LE changes in 0.32.0, and hosted MCP serves the same registry.
• offline orgs use <org> sets the default organization by ID or name, and the global --org <org> overrides it for one command. At login the CLI picks your only organization, or asks once when you have several. Switching organization clears the stored App ID and key.
• setup and apply reuse the API key this machine created for an application instead of creating another; keys create --set-default records it too.
• offline whoami names the stored credential, a developer session or an app key (--json adds credential).
• offline login prints the approval URL instead of opening a browser over SSH or on Linux with no display.
• offline init and new scaffolds start the local MCP server with @offline-protocol/cli@0.3.2.

Changes in 0.3.1

• offline create, offline add and the MCP tools resolve @offline-protocol/id-react-native 0.4.0, @offline-protocol/id-react 0.3.0 and @offline-protocol/pol 0.1.2. In these releases sendCode resolves to true and throws OfflineIdError when the server refuses the request; id-react-native 0.4.0 also attests every code request and sign-in.
• The React Native starters react-native-id-only and react-native-social include a native module for iOS App Attest and Android hardware key attestation, passed to OfflineAppProvider, and offline create adds the App Attest entitlement to the iOS target.
• The identity skill covers attestation for Expo and bare React Native, development mode for simulators and emulators, which Android devices sign in with degraded trust and which are refused, and OfflineIdError handling. Searches for attestation, App Attest or development mode find it.
• offline init and new scaffolds start the local MCP server with @offline-protocol/cli@0.3.1.

Changes in 0.3.0

• Every developer portal setup step has a command: offline apps status, offline apps native (register iOS and Android apps, detect them from the project, development builds, development mode, production mark, Android policy, history, Expo setup), offline apps origins, offline apps features and offline apply, which converges the application to the app block of offline.config.json. offline login --email accepts --code.
• Local MCP adds 16 tools that set up the application with the developer session; see setup tools. Hosted MCP adds app_status.

Changes in 0.2.9

• offline create, offline add and the MCP tools resolve SDK 0.31.0, so scaffolds install @offline-protocol/mesh-sdk 0.31.0.
• offline init and new scaffolds start the local MCP server with @offline-protocol/cli@0.2.9.

Changes in 0.2.8

• offline create, offline add and the MCP tools resolve the SDK release that was current when 0.2.8 shipped, 0.30.0, so its scaffolds install @offline-protocol/mesh-sdk 0.30.0.
• The registry adds the three bindings that 0.30.0 ships: offline-protocol-java on Maven Central, offline-protocol-c (the C API in the GitHub release archives) and the offline-protocol-flutter preview, from a checkout of the SDK. Flutter and Java prompts are answered with that package rather than a React Native plan.
• The registry notes cover the 0.30.0 telemetry fix: apps that call enableTelemetry on 0.26.0 to 0.29.0 should update.
• offline init and new scaffolds start the local MCP server with @offline-protocol/cli@0.2.8.

Changes in 0.2.7

• offline create, offline add and the MCP tools resolve the SDK release that was current when 0.2.7 shipped, 0.29.0 (0.2.6 resolved 0.27.0). The registry covers 0.28 and 0.29: Python on PyPI with the HTTP front, the Rust crates, the Swift and Android previews, the local API and the leaf node. Later SDK releases, starting with 0.30.0, reach the CLI with its next release, and hosted MCP serves them once that release is deployed.
• offline create --template offers three starter apps: orderup, stocksync and cowrite.
• offline init and new scaffolds start the local MCP server with @offline-protocol/cli@0.2.7.

Changes in 0.2.6

• The npm package metadata and README list support@offlineprotocol.com as the help contact.
• offline init and new scaffolds start the local MCP server with @offline-protocol/cli@0.2.6.

Changes in 0.2.5

• npm installs one platform binary, about 10 MB, instead of all five, about 50 MB. Keep optional dependencies enabled.
• The developer session from offline login --email renews while you use the CLI, and offline logout signs it out.
• On macOS and Linux, credentials are written atomically and owner-only. The local login callback limits request size and time.
• Starter templates are licensed under MIT-0, and each generated README lists the license of every Offline Protocol package the project uses.
• New scaffolds use @offline-protocol/id-react 0.2.0.

Login and logout

offline login
offline whoami --json

offline logout

What the CLI stores and sends

Initialize a project

offline init --app-id app_your_application_id

Start from a workflow

Local MCP

npx -y @offline-protocol/cli@0.3.3 mcp serve

Hosted MCP

Authorization: Bearer <app-api-key>
x-app-id: app_your_application_id

Public read-only endpoint

Setup tools

Connect your agent

claude mcp add offline-protocol -- npx -y @offline-protocol/cli@0.3.3 mcp serve

claude mcp add --transport http offline-protocol https://mcp.offlineprotocol.com/mcp --header "Authorization: Bearer $OFFLINE_API_KEY" --header "x-app-id: app_your_application_id"

{
  "mcpServers": {
    "offline-protocol": {
      "type": "http",
      "url": "https://mcp.offlineprotocol.com/mcp",
      "headers": {
        "Authorization": "Bearer ${OFFLINE_API_KEY}",
        "x-app-id": "app_your_application_id"
      }
    }
  }
}

[mcp_servers.offline-protocol]
command = "npx"
args = ["-y", "@offline-protocol/cli@0.3.3", "mcp", "serve"]

[mcp_servers.offline-protocol]
url = "https://mcp.offlineprotocol.com/mcp"
bearer_token_env_var = "OFFLINE_API_KEY"
http_headers = { "x-app-id" = "app_your_application_id" }

{
  "mcpServers": {
    "offline-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "@offline-protocol/cli@0.3.3",
        "mcp",
        "serve"
      ]
    }
  }
}

{
  "mcpServers": {
    "offline-protocol": {
      "url": "https://mcp.offlineprotocol.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:OFFLINE_API_KEY}",
        "x-app-id": "app_your_application_id"
      }
    }
  }
}

{
  "servers": {
    "offline-protocol": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@offline-protocol/cli@0.3.3",
        "mcp",
        "serve"
      ]
    }
  }
}

{
  "inputs": [
    {
      "type": "promptString",
      "id": "offline-api-key",
      "description": "Offline Protocol app API key",
      "password": true
    }
  ],
  "servers": {
    "offline-protocol": {
      "type": "http",
      "url": "https://mcp.offlineprotocol.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:offline-api-key}",
        "x-app-id": "app_your_application_id"
      }
    }
  }
}

{
  "mcpServers": {
    "offline-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "@offline-protocol/cli@0.3.3",
        "mcp",
        "serve"
      ]
    }
  }
}

{
  "mcpServers": {
    "offline-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "@offline-protocol/cli@0.3.3",
        "mcp",
        "serve"
      ]
    }
  }
}

Give the agent current instructions