Log inSubmit server
Offline Protocol logo

Offline Protocol

Helps coding agents find Offline Protocol SDKs, follow integration guides, plan implementations, and scaffold local apps.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Offline Protocol

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://mcp.offlineprotocol.com/public/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · TodayLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 10/28/2026, 11:17:32 PM

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://mcp.offlineprotocol.com/public/mcp

Overview

Offline Protocol connects coding agents to developer tools for finding SDK packages, reading integration guides and workflows, planning implementations, and scaffolding or integrating local applications. It runs through the published CLI over stdio with npx, or through a hosted MCP endpoint that requires an application API key and ID. Reach for it when an agent needs Offline Protocol-specific implementation guidance or project setup; it does not discover nearby devices, operate a mesh, or control live hardware.

Use cases

  • Find Offline Protocol SDK packages for an application
  • Read integration guides before implementing a feature
  • Plan an Offline Protocol application workflow
  • Scaffold a local project from agent instructions
  • Resolve package licenses during project setup

Key features

  • Offline Protocol SDK package discovery
  • Integration guide and workflow lookup
  • Implementation planning support
  • Local project scaffolding
  • Existing project integration
  • Stdio and hosted MCP deployment options

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

4/4 checks healthy over the last 15d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.6kPackage downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.

How Offline Protocol works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Offline Protocol

Offline Protocol is an MCP server that connects coding agents to Offline Protocol developer tools. Its main capabilities find SDK packages, read integration guides and workflows, plan implementations, scaffold local applications, and integrate projects. It runs locally through the Offline Protocol CLI or remotely through the hosted MCP endpoint.

Install it by registering the local stdio command `npx -y @offline-protocol/cli@latest mcp serve` with your MCP client, or use the client-specific plugin and extension commands in the repository. Local installation requires Node.js 18 or later and npx.

Yes, Offline Protocol works with Cursor through its local plugin or an MCP configuration file. Copy the plugin into Cursor's local plugins directory, or add the provided stdio server definition to the project or user MCP configuration and reload Cursor.

No, Offline Protocol does not control nearby devices or live hardware. Its tools support application development tasks such as finding SDKs, consulting integration workflows, planning implementations, and scaffolding or integrating projects.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOffline Protocol AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/offline-protocol?style=directory)](https://allmcps.com/mcp/offline-protocol)
HTML Embed
<a href="https://allmcps.com/mcp/offline-protocol"><img src="https://allmcps.com/api/badge/offline-protocol?style=directory" alt="Offline Protocol on AllMCPs" /></a>