Connects coding agents to developer tools to find SDK packages, read integration guides, and scaffold local applications.
Also known as Offline-Protocol/offline-protocol-agent-plugins, offline-protocol-agent-plugins, @offline-protocol/cli
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.3.3
- Last commit
- Nov 11, 2026
- License
- Apache-2.0
What is Offline Protocol MCP?
Offline Protocol connects coding agents to developer tools to find SDK packages, read integration guides, and scaffold local applications.
Summary generated from the project's README
About Offline Protocol MCP server
Offline Protocol provides a bridge between coding agents and developer tools to assist with application building. It allows AI clients to locate SDK packages, access integration guides, and scaffold new projects directly on a local machine. This server is designed for developers using MCP-compatible clients such as Claude Code, Cursor, VS Code, Cline, and Devin.
Users can run the server locally using the command npx -y @offline-protocol/cli@0.3.3 mcp serve, which requires Node.js 18 or later. Local execution does not require an account and sends no telemetry. Alternatively, developers can connect to a hosted version at mcp.offlineprotocol.com, which necessitates an application ID and an API key from the Offline Protocol developer portal. The tools focus on software development tasks like planning implementations and reading workflows rather than controlling hardware or mesh networks.
What you can do with it
- 1Locate SDK packagesAsk your coding agent to find specific Offline Protocol SDK packages for your project.
- 2Read integration documentationHave an AI client review integration guides and workflows to plan a software implementation.
- 3Scaffold local applicationsInstruct an agent to generate the initial structure of a project on your computer.
Written from the project's README. Every use case is checked against a quote from it.
How to install Offline Protocol MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Offline Protocol MCP in Claude Code
$ claude mcp add offline-protocol-agent-plugins -- npx -y @offline-protocol/cliInstall Offline Protocol MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"offline-protocol-agent-plugins": {
"command": "npx",
"args": [
"-y",
"@offline-protocol/cli"
]
}
}
}Install Offline Protocol MCP in VS Code
.vscode/mcp.json
{
"servers": {
"offline-protocol-agent-plugins": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@offline-protocol/cli"
]
}
}
}Install Offline Protocol MCP in VS Code CLI
$ code --add-mcp '{"name":"offline-protocol-agent-plugins","type":"stdio","command":"npx","args":["-y","@offline-protocol/cli"]}'Install Offline Protocol MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"offline-protocol-agent-plugins": {
"command": "npx",
"args": [
"-y",
"@offline-protocol/cli"
]
}
}
}Install Offline Protocol MCP in Codex
$ codex mcp add offline-protocol-agent-plugins -- npx -y @offline-protocol/cliInstall Offline Protocol MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.offline-protocol-agent-plugins] command = "npx" args = ["-y", "@offline-protocol/cli"]
Install Offline Protocol MCP in Gemini CLI
$ gemini mcp add -s user offline-protocol-agent-plugins npx -- -y @offline-protocol/cliInstall Offline Protocol MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"offline-protocol-agent-plugins": {
"command": "npx",
"args": [
"-y",
"@offline-protocol/cli"
]
}
}
}Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableoffline-protocol/offline-protocol-agent-plugins is public and reachablegithub.com/offline-protocol/offline-protocol-agent-plugins ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-11github.com/offline-protocol/offline-protocol-agent-plugins ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @offline-protocol/cliPass
- No critical advisory in the package or its dependenciesthe package checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubOffline 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/cli@0.3.3 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.
- Documentation: https://www.offlineprotocol.com/docs/tools/overview
- npm package: https://www.npmjs.com/package/@offline-protocol/cli
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/cli@0.3.3) 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/cli@0.3.3 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/cli@0.3.3","mcp","serve"]}'
For one workspace, copy distribution/clients/vscode.json to .vscode/mcp.json.
Cline
cline mcp install offline-protocol -- npx -y @offline-protocol/cli@0.3.3 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/cli@0.3.3 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/cli@0.3.3", "mcp", "serve"]
}
}
}
Zed, Continue, xAI and hosted configurations are in
distribution/clients/README.md and distribution/clients/priority-two.md.
What is in here
| Path | Contents |
|---|---|
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.json |
Gemini 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.yml |
Checks 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 security@offlineprotocol.com, not in public issues
(SECURITY.md).
Offline Protocol MCP questions
How do I add Offline Protocol MCP to Claude Code?
Run claude mcp add offline-protocol-agent-plugins -- npx -y @offline-protocol/cli in your terminal. Add --scope user to make it available in every project.
How do I add Offline Protocol MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What can the Offline Protocol agent do?
The agent can find SDK packages, read integration guides and workflows, plan implementations, and scaffold or integrate projects on your machine.
Does the tool control hardware or mesh networks?
No, the tools are designed to help build applications and do not operate mesh networks or control live hardware.
Do I need an account to use the local tools?
Local tools do not require an Offline Protocol account and do not send telemetry.
What is required to run the server?
You need Node.js 18 or later with npx installed.