TripHelm for OpenClaw

One triphelm planning skill and the existing remote MCP endpoint, https://triphelm.com/mcp, with a no-op OpenClaw entrypoint for package validation. OpenClaw handles setup, browser OAuth, token storage, and refresh. The entrypoint registers nothing; skills and MCP are declared in the manifest.

The skill covers all nine MCP tools: save detailed trips, show calendars, find reservations, incorporate supplied confirmations, and revise events or days without losing bookings. It reads fresh state before edits and returns the calendar link. The AI client plans; TripHelm persists the calendar.

Install from this checkout

Review the manifests, .mcp.json, and skill: the connection can read, create, edit, and delete the authorized account's trips. From the repository root:

openclaw plugins install ./plugins/triphelm --force
openclaw plugins inspect triphelm
openclaw skills list

--force acknowledges a trusted local source outside ClawHub; it does not bypass install-policy blocks. Accept the declared capabilities in OpenClaw's normal flow. OpenClaw loads the native no-op wrapper, skill triphelm, and MCP server triphelm; the Codex content manifest remains packaged for compatible clients. Start the Gateway if stopped, then use a new agent session.

Configure and log in

Check saved configuration first:

openclaw mcp list
openclaw mcp show triphelm

If the correct server exists, skip the add command. Otherwise, show reports an unknown server. Resolve a conflicting entry rather than overwriting it or creating aliases. CLI login uses saved MCP settings, not just bundle definitions:

openclaw mcp add triphelm \
  --url https://triphelm.com/mcp \
  --transport streamable-http \
  --auth oauth \
  --oauth-scope "openid profile email offline_access"

openclaw mcp login triphelm
openclaw mcp doctor triphelm --probe

Complete browser sign-in and consent. You can also use OpenClaw's MCP settings with the same values; saved config uses mcp.servers, not the .mcp.json wrapper. Never paste credentials into chat, commit tokens, or disable TLS verification. For diagnostics, use openclaw mcp status --json and openclaw mcp doctor triphelm; --probe checks connectivity after login.

Personal instances by default. Other senders on a shared agent may use the operator's account. Shared bots need OpenClaw's per-requester OAuth setup and separate isolation checks.

Use it

Ask "Show my trips," "Plan four days in Kyoto," or "Move dinner on day two to 7 PM." A saved plan is not an actual travel booking.

Inline calendars depend on the host's MCP Apps support and configuration. Text-only channels get a summary and itinerary link. Opening the web calendar may require separate browser sign-in; MCP login does not make private trips public.

Publish as a bundle

Upload only this directory as an archive through Plugin > Bundle plugin. Include .codex-plugin/plugin.json, .mcp.json, openclaw.plugin.json, package.json, openclaw.extension.mjs, and the planning skill. The root manifest supplies OpenClaw skills and MCP metadata. package.json declares the no-op entrypoint and the upload form's required openclaw.compat.pluginApi and openclaw.build.openclawVersion, based on the tested OpenClaw 2026.9.8 release. Package and manifest versions, and both MCP declarations, must stay identical.

Preview CLI publishing without uploading:

clawhub package publish ./plugins/triphelm \
  --family bundle-plugin \
  --version 0.1.1 \
  --dry-run

The version is also declared in package.json. Review the publisher, available package name, and exact files before submitting; the package name is editable in the form or with the CLI's --name option. New releases remain private until automated security checks and verification finish. The package is unpublished; no registry name is promised.

Validation and limits

Validation target: OpenClaw 2026.9.8. Package installation, the no-op wrapper, the single skill, MCP declaration discovery, saved configuration, and static OAuth diagnostics are checked in isolated state. Contract tests:

bun test scripts/lib/triphelm-plugin.test.ts
clawhub package validate ./plugins/triphelm --openclaw-version 2026.9.8 --out /tmp/triphelm-validation

Release 0.1.1 resolves the package-openclaw-entry-missing finding from 0.1.0. ClawHub's publish dry-run and required compatibility-field validation pass. Keep inspector --out outside this directory to avoid shipping generated reports. Local CLI success alone does not prove acceptance by the web publishing form.

Browser OAuth, authenticated tool discovery, list_trips, get_trip, refresh, and inline rendering remain unverified. Finish the read-only smoke test with normal login, list_trips, and get_trip for a returned trip; an empty account does not require creating a test trip. Follow protected-resource discovery to its issuer when diagnosing OAuth; do not change live auth to bypass failures.

Packaging references: OpenClaw bundles, OpenClaw MCP, and the inspected Camoufox bundle layout and Shopify no-op entrypoint.