Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Overview

ClawUp is a managed OpenClaw platform focused on:

  • One-click OpenClaw deployment
  • Bot memory inheritance (Fork From)
  • App-based extensibility (MCP + Webhooks)
  • Privacy-first operations (zero data retain by default)

Core management surfaces:

  • Settings -> App Registry (admin): register MCP/Hook apps
  • Apps -> Marketplace / Installed (user): bind apps to bots and manage lifecycle
  • Billing / Audits: recharge and operational traceability

Terminology:

  • MCP app: protocol-driven tool endpoint integrated into runtime.
  • Hook app: webhook-style endpoint integrated via hook-specific config/sync flow.

Use this docs site as the single entry for product usage and operations.

Quick Start

  1. Sign in with Google/GitHub/Wallet.
  2. Recharge balance in Billing.
  3. (Admin) Register MCP/Hook apps in Settings -> App Registry.
  4. Create your first bot.
  5. Open Apps -> Marketplace, select bot, and add needed apps.
  6. Configure channels.
  7. Test chat and monitor runtime status.

If you use Telegram webhook apps, verify and recover from Apps -> Installed -> Resync Webhook.

Create Bot

When creating a bot, configure:

  • Provider/model
  • API key
  • Runtime type and image
  • Restore source (optional)

The platform validates OpenClaw config before applying it.

After bot creation:

  1. Go to Apps -> Marketplace
  2. Select your bot
  3. Add required apps (MCP or Hook)
  4. Verify in Apps -> Installed

For Telegram webhook apps:

  • fill token/secret/allowed updates during install
  • use Resync Webhook after webhook URL/token changes

Apps & Webhooks

ClawUp now uses a unified App model for both MCP servers and Webhook integrations.

Architecture

The flow is split into two layers:

  1. Platform registration (admin):

    • Register app metadata once in Settings -> App Registry
    • App type can be MCP or Hook
    • Control status (active / disabled), endpoint, auth scheme, and visibility

  2. Per-bot binding (user):

    • Go to Apps -> Marketplace
    • Select target bot
    • Click Add to Bot
    • Fill app-specific credentials/config
    • Click Validate & Install

After binding, manage in Apps -> Installed.

MCP vs Hook

ClawUp uses one App model, but there are two integration styles:

  1. MCP App

    • Purpose: expose tools/capabilities through MCP protocol.
    • Typical endpoint: MCP HTTP/SSE endpoint.
    • Runtime behavior: bound into your claw runtime as an MCP app.

  2. Hook App

    • Purpose: webhook/event style integration (for example Telegram webhook workflows).
    • Typical endpoint: HTTP webhook target.
    • Runtime behavior: stores webhook config and executes hook-specific apply/sync flow.

In App Registry, Type controls which validation path and binding behavior are used.

Validate Behavior

Validate in App Registry is not just a ping:

  1. For MCP apps

    • ClawUp sends a JSON-RPC initialize probe.
    • Headers include:
      • Content-Type: application/json
      • Accept: application/json, text/event-stream
    • Success criteria: endpoint returns 2xx.
    • Reason: many MCP servers reject plain GET checks and require MCP handshake semantics.

  2. For Hook apps

    • ClawUp runs a basic HTTP reachability check (GET).
    • Success criteria: 2xx/3xx.

If validation fails, backend returns detailed failure text (status/body/request failure), and UI now shows validation status in the App Registry table.

Where To Register Apps

Open Settings and switch to App Registry tab.

Available actions:

  • Add App: create a new MCP/Hook registry item
  • Edit: update endpoint/auth/status/etc.
  • Enable / Disable: toggle app availability for users
  • Validate: run backend validation against the configured endpoint
  • Type Filter: All, MCP, Hook

Only node admins can access App Registry.

Where Users Install Apps

Open left nav Apps.

Tabs:

  • Marketplace: discover registered apps and add to selected bot
  • Installed: view installed app bindings for current bot and reconfigure/remove

Bot cards also include an Apps button that jumps directly to this page and preselects the bot.

Telegram Webhook App

For Telegram webhook style apps, Add to Bot shows extra fields:

  • Bot Token / API Key
  • Webhook Secret
  • Allowed Updates (comma-separated)
  • Drop pending updates

Then use Validate & Install.

Resync Webhook

In Apps -> Installed, Telegram webhook apps have a Resync Webhook action.

This calls:

  • POST /api/v1/bots/{id}/telegram/webhook/sync

Use this when:

  • webhook target URL changed
  • Telegram side webhook config drifted
  • token/secret rotated and you need re-apply

Operational Recommendation

Use this order for production:

  1. Admin registers app in App Registry
  2. Admin validates endpoint and enables app
  3. User installs app in Marketplace
  4. User verifies status in Installed
  5. For Telegram webhook apps, run Resync Webhook after token/URL changes

Restore & Migration

Fork From Existing Bot

Choose Restore Source = Fork From Existing Bot and pick a backup version.

Upload Local OpenClaw Backup

Get CLAWUP_BEARER_TOKEN first:

Recommended (production):

  1. Log in on ClawUp web.
  2. Open browser DevTools -> Application/Storage -> Cookies.
  3. Copy cookie clawup_token. Its value is CLAWUP_BEARER_TOKEN.

Verify token:

curl -sS https://api.clawup.org/api/v1/auth/me \
  -H "Authorization: Bearer <CLAWUP_BEARER_TOKEN>"

Download and use script:

curl -fsSL https://clawup.org/upload_openclaw_import.sh -o /tmp/upload_openclaw_import.sh
chmod +x /tmp/upload_openclaw_import.sh
/tmp/upload_openclaw_import.sh \
  --token <CLAWUP_BEARER_TOKEN> \
  --api-base https://api.clawup.org \
  --upload-id my-local-openclaw \
  --dir ~/.openclaw

Flow:

  1. Request upload ticket from backend.
  2. Upload tar directly to OSS via signed URL.
  3. Complete upload confirmation.
  4. Select uploaded backup version in Create Bot.

Billing

Current recharge methods:

  • Telegram channel coupon
  • Stripe recharge
  • Recharge card

Check billing logs and audit logs for full traceability.

FAQ

Why does chat return GATEWAY_NOT_READY?

Runtime may still be starting or gateway token/url is missing.

Why does chat return upstream 404?

Check ACK gateway URL template and runtime-router ingress routing.

How do I switch model safely?

Add model credentials first, then switch in chat or channel.

Where do I add MCP or Webhook integrations?

Two steps:

  1. Node admin registers app in Settings -> App Registry
  2. User installs/binds app in Apps -> Marketplace

Then manage binding in Apps -> Installed.

Telegram webhook app is not receiving updates. What should I do?

  1. Open Apps -> Installed
  2. Click Resync Webhook on your Telegram webhook app
  3. Verify backend env has:
    • TELEGRAM_COUPON_BOT_TOKEN
    • TELEGRAM_COUPON_WEBHOOK_TOKEN
    • TELEGRAM_COUPON_WEBHOOK_URL (or BACKEND_PUBLIC_BASE_URL)
  4. Recheck Telegram getWebhookInfo