Running OpenClaw in Production: Integrating with Your Mobile & Web Apps (Part I)

In just the last month, we have received a growing number of support and feature requests from both individual and enterprise customers looking to integrate OpenClaw into their mobile and web applications. Honestly, this caught us a little off guard — OpenClaw was originally designed as a personal automation tool. However, its trajectory has shifted quickly.

Adoption is accelerating, and more importantly, OpenClaw is starting to appear inside real organizational workflows. Work like When OpenClaw Meets Hospital: Toward an Agentic Operating System for Dynamic Clinical Workflows illustrates how OpenClaw-based systems can coordinate clinical decision-making, automate documentation, and manage dynamic workflows in high-stakes hospital environments — a far cry from personal automation.

This trend is not limited to healthcare. mesibo serves customers across telemedicine, hospitality, travel, finance, government, and other sectors, and we are seeing a consistent pattern: organizations want to embed OpenClaw directly into their user interaction layer — booking assistance, itinerary queries, guest services, real-time customer support and more. The volume of requests quickly reached the point where answering each one individually was no longer sustainable, so instead we built the mesibo OpenClaw Channel Plugin: a single, reusable integration that lets OpenClaw plug directly into any mobile or web application and operate as a full agentic AI participant in real-time conversations.

In Part 1, we briefly introduce mesibo and show how to add it to your app — it takes minutes, not days. We then walk through the full OpenClaw integration. If you are already running a mesibo-powered app, skip the introduction and jump straight to the integration section.

What is mesibo?

mesibo is a real-time communication platform providing APIs for messaging, voice and video calling, conferencing, and chat automation in mobile and web applications. It exposes a unified API for user-to-user communication, and is available both as a cloud service and as a fully self-hosted, on-premise deployment inside your own infrastructure.

In this article, we use the mesibo API together with the mesibo OpenClaw plugin to wire OpenClaw into your application.

If you are new to mesibo, start with the Get Started Tutorial to understand the core concepts and build a working sample app with messaging and calling. You can then use that sample app to test your OpenClaw integration end-to-end.

Integrating OpenClaw with Your Mobile and Web Apps

This section assumes OpenClaw is already installed and running in your environment. If not, complete the OpenClaw setup before proceeding. It also assumes basic familiarity with mesibo.

The integration is very simple: create a mesibo user, assign it to your OpenClaw instance, and you’re done. OpenClaw then behaves like any other regular user (endpoint) in your mesibo app. Your users can interact with it in real time from Android, iOS, Flutter, or web — exactly as they would with any other mesibo user. No special handling is required on the app side.

On the OpenClaw side, the integration is entirely handled by the mesibo OpenClaw Channel Plugin, which connects OpenClaw to mesibo and can be installed with a single command. In this article we use the plugin directly from the npm registry. If you need to customize or extend it, the source is on GitHub which we will cover in Part 2.

Step 1 — Install the mesibo OpenClaw Plugin

Install the plugin from the npm registry into your OpenClaw instance:

$ openclaw plugins install @mesibo/openclaw-channel

If you have an older version installed, remove it first:

$ openclaw plugins uninstall mesibo --force

$ openclaw plugins install @mesibo/openclaw-channel

Confirm the plugin loaded:

$ openclaw plugins list

You should see an entry like:

│ @mesibo/     │ mesibo   │ openclaw │ loaded   │ global:mesibo/index.ts   │ 1.0.13   │

Step 2 — Create a mesibo User for OpenClaw

OpenClaw connects to mesibo as a regular user. The next step is to create this user and obtain an access token.

If you haven’t already, go through the mesibo Get Started Tutorial which covers how to create users and generate access tokens. You will need your mesibo App Token to make the request below.

Send the following request to https://api.mesibo.com/backend/, substituting your actual App Token. If you are self-hosting mesibo, replace this with your own backend API URL, the rest of the integration works identically either way. In this example we use com.mesibo.openclaw as the App ID, but replace it with whatever is appropriate for your app.

{
  "op": "useradd",
  "token": "YOUR_APP_TOKEN",
  "user": {
    "address": "1234567890",
    "token": {
      "appid": "com.mesibo.openclaw",
      "expiry": 525600
    }
  }
}

A successful response looks like:

{
    "user": {
        "uid": "5302",
        "token": "MIIb_w_JbrDfV5lMOengI8PtAINjH93lfQK10bqdIdhN82w3G_0J4jQ_kO8lJbQP9Dpjcc0jfGa9sWrVTc1ZRna9sWrVkXfrTJbjBz"
    },
    "op": "useradd",
    "result": true
}

The token field in the response is the user access token you will configure in OpenClaw in the next step.

Step 3 — Configure the mesibo Channel in OpenClaw

Run the configuration wizard:

$ openclaw configure --section channels

Work through the prompts:

1. Where will the Gateway run? — select Local and press Enter.

2. Channels — select Configure/link and press Enter.

3. Select a channel — select Mesibo and press Enter.

You will now see the mesibo configuration screen. Enter:

• The user access token generated in Step 2
• The App ID you used when creating the token (com.mesibo.openclaw in this example)

You can also configure an allow-list of authenticated mesibo users who are permitted to interact with OpenClaw, or leave it empty to allow all users, which is fine for initial testing.

Once you save, the wizard will return to the channel selection screen. Select Finished and press Enter. Configuration is saved and the wizard exits.

Step 4 — Restart OpenClaw and Verify

Restart OpenClaw:

openclaw gateway

Check the logs for these lines confirming a successful connection:

[mesibo] startAccount called for accountId=default
[mesibo] connecting (appId=com.mesibo.openclaw)
[mesibo] connection status: ONLINE
[mesibo] connected, listening for messages

Now send a test message from your app to OpenClaw’s mesibo address — 1234567890 in this example. You should see the inbound message logged:

[mesibo] inbound message from=<your-address> id=<msg-id>

And within moments, a reply from your OpenClaw agent lands back in your app.

That’s it. In a handful of commands and a few minutes of configuration, you have a fully capable agentic AI embedded directly in your app — reachable from Android, iOS, Flutter, and web, without a single line of complicated glue code.

What makes this pattern powerful is that your application doesn’t change at all. Swap out the OpenClaw user address for a different agent, or run multiple agents in parallel, and the architecture holds. The next article in this series goes further — building a custom channel plugin from scratch, giving you full control over routing logic, authentication, message transformation, and multi-agent orchestration.

If you run into issues or want help adapting this for your specific deployment, reach out to us here. We are actively working with teams deploying this in production across a range of industries and are happy to help you get there too.