Connecting to OpenClaw

This page is the current technical guide for OpenClaw and Fluent.

If you want the plain-language overview first, start here:

• Using Fluent with AI Apps

Current Status

OpenClaw is part of the overall Fluent integrations story, but it does not yet have the same first-class setup assets that Claude and Codex have in this repo.

Today, this means:

• there is no dedicated openclaw scaffold target in npm run scaffold:mcp
• there is no checked-in OpenClaw plugin template in this repo
• there is no published OpenClaw-specific config artifact here yet

What Is Available Today

The supported, documented runtime path remains Fluent OSS:

npm run oss:start -- --host 127.0.0.1 --port 8788

Fluent OSS exposes the same core MCP surface used by the other documented clients:

• http://127.0.0.1:8788/mcp
• bearer-token auth for OSS
• the same capabilities, domains, and domain tools documented elsewhere in this site

Recommended Setup Approach Right Now

If you are experimenting with OpenClaw today, treat Fluent as the backend context/tool layer and use the same OSS runtime you would use for Claude or Codex.

The practical checklist is:

1. Start Fluent OSS locally or on your server.
2. Bootstrap or print your OSS token.
3. Confirm Fluent is healthy.
4. Connect OpenClaw to the Fluent MCP endpoint using OpenClaw's own external-tool or MCP registration flow, if your OpenClaw deployment supports that pattern.
5. Verify the connection by asking for Fluent capabilities first.

Useful commands:

npm run oss:token:bootstrap
npm run oss:start -- --host 127.0.0.1 --port 8788
npm run oss:token:print
curl http://127.0.0.1:8788/health

Verification

As with the other clients, the first useful check is:

"What are my Fluent capabilities?"

That should confirm that OpenClaw can reach Fluent and that Fluent is returning:

• contract version
• available and ready domains
• onboarding state
• tool discovery hints

What Is Still Missing

This repo does not yet publish a finalized OpenClaw-specific setup flow.

That means this guide is intentionally conservative:

• no OpenClaw-specific config format is documented here yet
• no OpenClaw-specific auth walkthrough is documented here yet
• no first-class plugin/install path is documented here yet

Once the OpenClaw integration path is finalized, this page should be expanded with exact setup steps.

Next Steps

• Using Fluent with AI Apps
• Client Configuration
• Connecting to Claude
• Connecting to Codex