Offline Protocol MCP server
Commit Nov 11, 2026Connects coding agents to developer tools, SDK packages, and integration guides to help plan and scaffold project implementations.
Also known as Offline-Protocol/offline-protocol-agent-plugins, hosted
- 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, SDK packages, and integration guides to help plan and scaffold project implementations.
Summary generated from the project's README
About Offline Protocol MCP server
Offline Protocol provides a bridge between coding agents and developer resources to assist with project planning and scaffolding. It allows AI clients like Claude Code, Cursor, Devin, and VS Code to access SDK packages, integration guides, and specific workflows. This connection helps agents move from high-level planning to actual implementation on your local machine.
Developers can choose between running a local MCP server using the command npx -y @offline-protocol/cli@0.3.3 mcp serve or connecting to a hosted version at mcp.offlineprotocol.com. The local setup requires Node.js 18 or later and does not need an account or telemetry. If you use the hosted server, you must provide an application ID and an API key from the developer portal. This tool focuses on software development tasks and does not control hardware or manage mesh networks.
What you can do with it
- 1Scaffold new project implementationsAsk your coding agent to set up the initial structure and files for a new application using available SDKs.
- 2Research integration workflowsHave an AI client read through official documentation to understand how to implement specific features.
- 3Identify project dependenciesUse the agent to find and resolve the necessary SDK packages required for your development task.
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 --transport http hosted https://mcp.offlineprotocol.com/mcpInstall Offline Protocol MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"hosted": {
"url": "https://mcp.offlineprotocol.com/mcp"
}
}
}Install Offline Protocol MCP in VS Code
.vscode/mcp.json
{
"servers": {
"hosted": {
"type": "http",
"url": "https://mcp.offlineprotocol.com/mcp"
}
}
}Install Offline Protocol MCP in VS Code CLI
$ code --add-mcp '{"name":"hosted","type":"http","url":"https://mcp.offlineprotocol.com/mcp"}'Install Offline Protocol MCP in Codex
$ codex mcp add hosted --url https://mcp.offlineprotocol.com/mcpInstall Offline Protocol MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.hosted] url = "https://mcp.offlineprotocol.com/mcp"
Install Offline Protocol MCP in Gemini CLI
$ gemini mcp add -s user --transport http hosted https://mcp.offlineprotocol.com/mcpInstall Offline Protocol MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"hosted": {
"url": "https://mcp.offlineprotocol.com/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- 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)Not 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 packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- 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 handshakeHTTPS endpoint answered 401 (sign-in required)Pass
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 --transport http hosted https://mcp.offlineprotocol.com/mcp 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 local MCP server require an account or send telemetry?
No, local tools do not require an Offline Protocol account and do not send any telemetry.
What is required to use the hosted MCP server?
To use the hosted server, you need an application API key and an application ID from the Offline Protocol developer portal.
Can this server control live hardware?
No, the tools are designed to help build applications and do not operate mesh networks or control live hardware.