feat: add HTTP MCP serving

.changeset/fuzzy-carpets-serve-http.md

@@ -0,0 +1,6 @@
+---
+"@caplets/core": minor
+"caplets": minor
+---
+
+Add `caplets serve` transport options, including opt-in Hono Streamable HTTP MCP serving with optional Basic Auth, health/info endpoints, and no-arg help behavior.

.changeset/remote-native-caplets.md

@@ -0,0 +1,8 @@
+---
+"@caplets/core": minor
+"@caplets/opencode": minor
+"@caplets/pi": minor
+"caplets": patch
+---
+
+Add remote Caplets service support for native integrations, including remote-backed OpenCode and Pi native tools plus documentation for MCP-backed Codex and Claude Code remote connections.

.opencode/opencode.json

@@ -1,6 +1,16 @@
 {
   "$schema": "https://opencode.ai/config.json",
-  "plugin": ["@caplets/opencode@file:./packages/opencode"],
+  "plugin": [
+    [
+      "@caplets/opencode@file:./packages/opencode",
+      {
+        "mode": "remote",
+        "remote": {
+          "url": "http://localhost:5387/mcp"
+        }
+      }
+    ]
+  ],
   "permission": {
     "external_directory": {
       "~/.config/caplets/": "allow",

.pi/settings.json

@@ -1,3 +1,9 @@
 {
-  "packages": ["npm:@caplets/pi@file:../../packages/pi"]
+  "packages": ["npm:@caplets/pi@file:../../packages/pi"],
+  "caplets": {
+    "mode": "remote",
+    "remote": {
+      "url": "http://localhost:5387/mcp"
+    }
+  }
 }

README.md

@@ -103,6 +103,33 @@ The Claude Code and Codex commands install from this GitHub repository through e
 plugin marketplace flow; users do not need to clone the repository manually. Plugin MCP
 configs run `caplets serve` directly, so install the Caplets CLI globally first.
 
+### Remote Caplets service
+
+OpenCode and Pi can use native `caplets_<id>` tools backed by a remote Caplets HTTP service. Codex, Claude Code, and any MCP client can connect to the same remote MCP endpoint directly.
+
+Start a local HTTP service:
+
+```sh
+caplets serve --transport http --host 127.0.0.1 --port 5387 --path /mcp
+```
+
+`caplets serve --transport http` serves plain HTTP. For non-loopback or network access, expose it only through HTTPS/TLS (for example, a reverse proxy or secure tunnel) and enable Basic Auth; Basic Auth over plain HTTP exposes credentials. Keep credentials out of plugin manifests:
+
+```sh
+CAPLETS_SERVER_PASSWORD=... caplets serve --transport http --host 127.0.0.1 --port 5387 --path /mcp
+```
+
+Native integrations read remote client settings from environment variables:
+
+```sh
+CAPLETS_REMOTE_URL=https://caplets.example.com/mcp \
+CAPLETS_REMOTE_USER=caplets \
+CAPLETS_REMOTE_PASSWORD=... \
+opencode
+```
+
+For MCP-backed Codex or Claude Code configs, point the agent's MCP server entry at the remote URL using that agent's supported HTTP MCP configuration. If Basic Auth is needed, use the agent's secure secret or environment interpolation mechanism rather than hardcoding credentials.
+
 ## Convert Existing Tooling
 
 Caplets is designed to convert what you already use into agent-friendly capability domains.