mcpField
O
Offline Protocol

Offline Protocol

Local
offlineprotocol.comDeveloper Tools0Updated 4d ago

About Offline Protocol

Offline Protocol agent plugins connect coding agents and MCP clients to tools for finding SDK packages, reading integration guidance, planning, and scaffolding local applications. They can use a local CLI server or a hosted MCP server; the tools do not operate devices or hardware.

Key features

  1. 01Find Offline Protocol SDK packages
  2. 02Read integration guides and workflows
  3. 03Plan application implementations
  4. 04Scaffold or integrate local projects
  5. 05Use local or hosted MCP server configuration

Use cases

  1. 01Find an SDK package for an application
  2. 02Review steps for integrating an SDK
  3. 03Plan and scaffold a local application project

MCP support

The plugins configure clients to run the local server with `npx -y @offline-protocol/[email protected] mcp serve` or connect to https://mcp.offlineprotocol.com/mcp. The tools support application development, not device discovery or live hardware control.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"com-offlineprotocol-cli": {
"command": "npx",
"args": [
"-y",
"@offline-protocol/cli"
]
}
}
}
Run commandnpx -y @offline-protocol/cli

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@offline-protocol/cli0.2.9

Tools

18

Saved tool list · updated 3d ago

This tool takes no parameters.

Details

From the project README

Offline Protocol agent plugins

Plugins, skills and MCP configuration that connect coding agents (Claude Code, Codex, Cursor, Gemini CLI, VS Code, Cline, Devin and other MCP clients) to the Offline Protocol developer tools. Your agent can find Offline Protocol SDK packages, read integration guides and workflows, plan an implementation, and scaffold or integrate a project on your machine.

Every configuration runs the local MCP server from the published Offline Protocol CLI, npx -y @offline-protocol/[email protected] mcp serve, or connects to the hosted MCP server at https://mcp.offlineprotocol.com/mcp. The tools help you build an application. They do not discover nearby devices, operate a mesh or control live hardware.

This repository is generated from the Offline Protocol CLI source by its export-agent-plugins.mjs script. SOURCE.json records the source commit and a sha256 for every file. Changes are made in the source and exported here; pull requests to this repository are reviewed and applied upstream.

Requirements

Node.js 18 or later with npx. The first run downloads the pinned CLI (@offline-protocol/[email protected]) from npm. Local tools need no Offline Protocol account and send no telemetry. The hosted server needs an application API key and its application ID from https://dev.offlineprotocol.com.

Install

Claude Code plugin
claude plugin marketplace add https://github.com/Offline-Protocol/offline-protocol-agent-plugins.git
claude plugin install offline-protocol@offline-protocol
Codex
codex plugin marketplace add https://github.com/Offline-Protocol/offline-protocol-agent-plugins.git
codex plugin add offline-protocol@offline-protocol

Or add only the MCP server:

codex mcp add offline-protocol -- npx -y @offline-protocol/[email protected] mcp serve
Cursor

Copy plugins/offline-protocol into ~/.cursor/plugins/local/offline-protocol and reload Cursor. For the MCP server alone, put the contents of distribution/clients/mcp-stdio.json in .cursor/mcp.json or ~/.cursor/mcp.json, or use the install link in distribution/clients/README.md.

Gemini CLI extension

The repository root is a Gemini CLI extension (gemini-extension.json).

gemini extensions install https://github.com/Offline-Protocol/offline-protocol-agent-plugins
VS Code with GitHub Copilot
code --add-mcp '{"name":"offline-protocol","type":"stdio","command":"npx","args":["-y","@offline-protocol/[email protected]","mcp","serve"]}'

For one workspace, copy distribution/clients/vscode.json to .vscode/mcp.json.

Cline
cline mcp install offline-protocol -- npx -y @offline-protocol/[email protected] mcp serve
Devin

Devin CLI:

devin plugins install Offline-Protocol/offline-protocol-agent-plugins#plugins/offline-protocol

Devin (web): add a custom MCP server with transport stdio, command npx and arguments -y @offline-protocol/[email protected] mcp serve. Devin Desktop: distribution/clients/devin-desktop.json.

Any other MCP client

Use this server definition (also in distribution/clients/mcp-stdio.json):

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

Zed, Continue, xAI and hosted configurations are in distribution/clients/README.md and distribution/clients/priority-two.md.

What is in here

PathContents
plugins/offline-protocol/The plugin: manifests for Claude Code, Codex and Cursor, MCP configuration, the integration skill and the logo
.claude-plugin/, .cursor-plugin/, .agents/plugins/Marketplace files that point at the plugin
gemini-extension.jsonGemini CLI extension manifest
distribution/clients/Ready-to-merge MCP configuration for other clients
distribution/cline/offline-protocol/Cline marketplace entry
distribution/mcp-registry/Official MCP Registry records
.github/workflows/validate.ymlChecks that run on every push and pull request: file hashes against SOURCE.json, manifest consistency, registry schema validation and a secret scan

Releases are tagged v<version>, where the version is the one in gemini-extension.json and the plugin manifests. The plugin version is separate from the CLI version it launches.

License, privacy and security

The plugin files are licensed under the Apache License 2.0 (LICENSE). The Offline Protocol CLI they launch is also Apache-2.0; SDKs it installs into your projects keep their own licenses, reported by the resolve_packages tool. The Offline Protocol name and logo are trademarks (NOTICE). Using hosted Offline Protocol services is governed by the developer terms at https://www.offlineprotocol.com/legal/developer-terms and the privacy policy at https://www.offlineprotocol.com/privacy. Your agent client and model provider handle tool inputs and results under their own terms.

Report security issues to [email protected], not in public issues (SECURITY.md).

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.