# Offline Protocol [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/Offline-Protocol/offline-protocol-agent-plugins  
**GitHub Stars:** 0  
**npm Downloads (last month):** 1575  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/offline-protocol

## Description
Find Offline Protocol SDK packages, read integration guides, plan and scaffold local apps.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Offline Protocol does

Offline Protocol gives coding agents access to Offline Protocol development resources and project-building workflows. Its capabilities cover finding relevant SDK packages, reading integration documentation, planning an implementation, and creating or integrating a project on the local machine.

The repository contains agent plugins, MCP configuration, client-specific installation files, and an integration skill. It supports use through several coding-agent ecosystems, including Claude Code, Codex, Cursor, Gemini CLI, VS Code with GitHub Copilot, Cline, and Devin. Additional client configuration files are included for other MCP-compatible applications.

## How it works

The local setup launches the Offline Protocol CLI with npx and exposes it as an MCP server over stdio. On first use, npx downloads the CLI package from npm. A generic server definition can be added to an MCP client with `npx -y @offline-protocol/cli@latest mcp serve`, while client-specific files and commands are available in the repository's distribution directories.

A hosted option is also available at `https://mcp.offlineprotocol.com/mcp`. Hosted access uses an application API key together with the application ID from the Offline Protocol developer portal. Local tools do not require an Offline Protocol account and do not send telemetry.

The repository is generated from the Offline Protocol CLI source. Its export process records source and file-integrity information, while validation checks cover manifests, registry data, hashes, and secrets.

## Setup and configuration

Node.js 18 or newer and npx are required for the local server. Installation varies by client:

- Claude Code, Codex, Gemini CLI, Cline, and Devin provide commands that install the plugin or extension.
- Cursor can load the local plugin or an MCP configuration file.
- VS Code can register the server with `code --add-mcp` or use a workspace `.vscode/mcp.json` file.
- Other MCP clients can use the stdio definition from `distribution/clients/mcp-stdio.json`.

The repository also includes configurations for Zed, Continue, xAI, hosted deployments, and Devin Desktop. The plugin release version and the CLI version it launches are separate, so their version metadata should not be treated as interchangeable.

## Tools and capabilities

The agent-facing workflow supports:

- Locating Offline Protocol SDK packages
- Reading integration guides and workflows
- Planning an application implementation
- Scaffolding a local project
- Integrating Offline Protocol into an existing project
- Resolving package information, including SDK license details

These capabilities are intended to help build applications. They are not interfaces for discovering nearby devices, managing a mesh, or operating live hardware.

## Limitations and notes

SDKs added to projects retain their own licenses; package license information is reported by the package-resolution capability. The plugin and CLI are licensed under Apache-2.0, while the Offline Protocol name and logo are trademarks. Hosted services are subject to Offline Protocol developer terms and privacy policies, and the agent client and model provider apply their own handling policies to tool inputs and results.

Security issues should be reported privately to security@offlineprotocol.com rather than through public issues.

_Full upstream README: https://allmcps.com/mcp/offline-protocol/readme_