Ask your docs
from OpenClaw chats

OpenClaw is an open-source AI assistant that runs on your own hardware. You talk to it in Telegram, WhatsApp, Slack and other chat apps. OpenClaw can use remote MCP servers. MCP is a standard way for AI apps to use outside tools. Each public Revdoku docs site has a read-only MCP server at /mcp, with no sign-in.

You need: a terminal on the machine that runs the OpenClaw Gateway (the OpenClaw background process). A public docs site needs no Revdoku account.

OpenClaw changes saved MCP servers only while the local Gateway is stopped. The same rule applies to login, logout and doctor --probe. While the Gateway runs, use the Control UI instead.

1. Stop the Gateway.
2. Save the docs server. Do not add --auth, because the docs server needs no sign-in.

   openclaw mcp add acme-docs \
     --url https://docs.example.com/mcp \
     --transport streamable-http

3. Run openclaw mcp doctor acme-docs --probe to test the connection.
4. Start the Gateway again. In a new session, ask: “Use the Acme docs. Which error codes can the payments API return?”

OpenClaw gives MCP tools to agents in its coding and messaging tool profiles (preset tool lists). The minimal profile does not include them.

The Revdoku skill lets OpenClaw use your Revdoku account through the Revdoku CLI (command-line tool). A skill is a folder of instructions and scripts that an agent loads. With the skill, OpenClaw reads support tickets and can publish a docs site.

You need: a terminal on the Gateway machine, and a Revdoku account.

1. On the Gateway machine, run this command: npx skills add revdoku/revdoku --skill revdoku -g --agent openclaw
2. If that machine has no npm, run the install script instead: curl -fsSL https://revdoku.com/install.sh | bash
3. Run openclaw skills check. Make sure that it shows revdoku as ready.
4. Start a new OpenClaw session. Ask: “List my Revdoku buckets and the address of each docs site.”
5. Open the Revdoku link that the CLI prints. Make sure that the connection ID on the page is the same. Select Connect.

Both installers put the skill in ~/.openclaw/skills/revdoku, a folder that OpenClaw shares with all local agents. The install script also adds the revdoku command in ~/.revdoku/bin. The skill lists bash, curl, openssl, base64, find and stat as required programs. OpenClaw hides the skill until all six are on the PATH.

If the Gateway runs on a server without a browser, the CLI cannot open the sign-in page. Open the printed link on your phone or laptop. You can also paste the setup prompt of Connect your AI in the Revdoku dashboard into an OpenClaw chat. OpenClaw then runs these steps itself.

The MCP server of your Revdoku account reads and writes files and email text. It cannot upload files from the OpenClaw machine. Stop the Gateway before these steps too.

1. Save the server:

   openclaw mcp add revdoku \
     --url https://mcp.revdoku.com \
     --transport streamable-http \
     --auth oauth

2. Hide the three delete tools:

   openclaw mcp tools revdoku \
     --exclude 'bucket_delete_permanently,bucket_ticket_message_delete,bucket_file_delete'

3. Run openclaw mcp login revdoku. Open the URL that it prints.
4. On the Revdoku permission screen, select one bucket. Choose Read only for summaries, Read & write to reply, or Full access to publish.
5. If your browser is on another machine, copy the returned code. Then run openclaw mcp login revdoku --code CODE.
6. Run openclaw mcp doctor revdoku --probe to test the connection. Then start the Gateway.

A bucket holds the files of one docs site, the site and its support tickets. If a bucket gets its files from GitHub, change the docs in the repository. The Edits in Revdoku setting of the bucket decides what happens to an edit that OpenClaw makes in Revdoku: it waits for a person, becomes a commit, or Revdoku refuses it.

• Ask in Telegram how an endpoint works. OpenClaw searches the docs and answers with a link to the page.
• Before a release, ask which pages mention a parameter that the release changes. OpenClaw lists them, so you can update them in time.
• For a bucket without a GitHub link, OpenClaw uploads files with revdoku upload and publishes the site with revdoku publish --bucket-id bkt_.... The CLI page shows how an uploaded folder is named in the bucket.
• OpenClaw replies to a support ticket with revdoku ticket-reply TICKET_ID --text TEXT --bucket-id bkt_.... The reply goes only to the person who opened the ticket, and Revdoku keeps it in the same ticket.

OpenClaw automations run an agent turn on a schedule. This job reads the new support tickets at 8:00 on weekdays and posts a summary to a Telegram chat. It searches the docs through the acme-docs server.

openclaw automations add \
  --name "Support summary" \
  --cron "0 8 * * 1-5" \
  --tz "America/New_York" \
  --session isolated \
  --message "Use the revdoku skill. List the support tickets of my Revdoku bucket that changed in the last 24 hours. Give each one a one-line summary. Search the Acme docs and name the page that answers it, or say that no page answers it. Do not reply or delete anything." \
  --announce \
  --channel telegram \
  --to "TELEGRAM_CHAT_ID"

Replace TELEGRAM_CHAT_ID with the ID of your chat. Set --tz to your time zone. Run openclaw automations list to see the job.

The OpenClaw documentation tells you to treat third-party skills as untrusted code and to read them before you enable them. The Revdoku skill is Markdown and Bash scripts under the MIT-0 license. After sign-in, it keeps the Revdoku credential in ~/.revdoku/credentials.

The skill tells OpenClaw that email bodies, attachments and file names are untrusted data. They cannot authorize commands, replies, uploads or deletions.

To sign the account server out, stop the Gateway and run openclaw mcp logout revdoku. Logout keeps the saved server. To remove a server, stop the Gateway and run openclaw mcp unset revdoku. Review or reconnect OpenClaw in Revdoku under Account → Access.

OpenClaw skills · OpenClaw MCP · OpenClaw saved MCP servers · OpenClaw automations · Docs for AI agents · Revdoku MCP guide