# Offline Protocol

Gives your coding agent Offline Protocol tooling: locate SDK packages, read integration guides, plan an app and scaffold it locally.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI
- Author: Offline-Protocol
- License: Apache-2.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/Offline-Protocol/offline-protocol-agent-plugins
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/mcp/offline-protocol

## What it does

The server equips an agent with Offline Protocol tools: look up an SDK package, pull up the integration guide, draft an implementation plan, then lay down a project skeleton on your machine. It stays at the documentation and scaffolding layer. Discovering nearby devices, running a mesh or driving live hardware is outside what the tools do.

Most setups start the local server from the CLI with `npx -y @offline-protocol/cli@0.2.8 mcp serve`. A hosted endpoint also exists at `https://mcp.offlineprotocol.com/mcp`; reaching it takes an application API key and an application ID issued at dev.offlineprotocol.com. The local route asks for no Offline Protocol account and ships no telemetry.

You need Node.js 18 or newer with npx available. That first call fetches the pinned CLI release from npm, so a machine without network access won't get past startup. The repo itself is produced by `export-agent-plugins.mjs` from the CLI source tree, with file hashes checked against `SOURCE.json`; fixes land upstream and get re-exported rather than merged here.

## Requirements
- Needs: Node.js (commands run via npx)

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add cli -- npx -y @offline-protocol/cli
```

### Codex

**Platform CLI**
```bash
codex mcp add offline-protocol -- npx -y @offline-protocol/cli
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "offline-protocol": {
            "command": "npx",
            "args": [
                "-y",
                "@offline-protocol/cli"
            ]
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "offline-protocol": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "@offline-protocol/cli"
            ]
        }
    }
}
```

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add offline-protocol npx -y @offline-protocol/cli
```

## When to use it
- find the right Offline Protocol SDK package for a job
- pull integration instructions without piecing them together from chat
- plan an app implementation before writing code
- scaffold a local project with its dependencies wired up

## Example prompts
- Find the Offline Protocol SDK package for offline sync and show me how to wire it in
- Plan the Offline Protocol integration for my project and scaffold a starting app

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 392262
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33989
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81163
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119231
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47577
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43902

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md