Cuiar
Sign inDownload

OpenClaw + Cuiar

Text a question. Get it from your account.

  • ~/.openclaw/openclaw.json
  • OAuth or a key header
  • Replies in your chat app
Set it up Get Cuiar

OpenClaw lives in the chat apps you already use. You ask it where your parcel is, or if your padel court is free, and the answer is behind a login.

OpenClaw opens your Personal workspace in Cuiar, signs in with the vault and reads the page. Steps that pay go to the Cuiar agent with run_task, and it asks you first.

A phone with a chat. The user asks where an order is. OpenClaw answers that it is checking the shop in Cuiar, then replies with the delivery day and a small picture of the order page.

Setup

Add Cuiar to the gateway.

Do this on the machine that runs the OpenClaw gateway. It can be another machine; it reaches Cuiar over the internet.

  1. 1

    Add the server

    Set transport yourself. Without it, OpenClaw uses SSE.

    ~/.openclaw/openclaw.json
    {
  mcp: {
    servers: {
      cuiar: {
        url: "https://mcp.cuiar.com/mcp",
        transport: "streamable-http",
        auth: "oauth",
      },
    },
  },
}
  2. 2

    Sign in

    openclaw mcp login cuiar
  3. 3

    Check and load it

    openclaw mcp doctor --probe
openclaw mcp reload
  4. 4

    Text it

    Which Cuiar workspaces do I have?

Other ways to connect

  • An API key

    Put CUIAR_API_KEY=cuiar_... in ~/.openclaw/.env, with a key that has the mcp scope. OpenClaw ignores a fixed Authorization header while auth is oauth, so use one or the other.

    ~/.openclaw/openclaw.json
    {
  mcp: {
    servers: {
      cuiar: {
        url: "https://mcp.cuiar.com/mcp",
        transport: "streamable-http",
        headers: { Authorization: "Bearer ${CUIAR_API_KEY}" },
      },
    },
  },
}

  • Local stdio

    On the machine with the Cuiar app, after cuiar login.

    openclaw mcp add cuiar --command cuiar --arg mcp

Route

The gateway keeps the session.

The gateway holds the MCP session and the tokens. Each step is a tool call that your model plan pays for, so a question in chat uses no Cuiar credits.

Remote MCPmcp.cuiar.com/mcp
Best fit
OAuth with openclaw mcp login, or a key header.
Local MCPcuiar mcp
Works
When the gateway runs on the computer with the Cuiar app.
CLIcuiar exec
Works
Through the exec tool, with exec approvals. A Docker sandbox does not have the cuiar binary.
Routineson a schedule
Works
OpenClaw Automations reply in a chat. A Cuiar routine emails the result and needs no gateway.

Example tasks

Questions you text

  • 01

    Track a parcel

    “Where is my order from the outdoor shop?”

    Personal workspace, vault sign-in, the order page and the carrier link.

  • 02

    Book a court

    “Book a padel court on Saturday from 10:00 to 11:30 at my club.”

    run_task. Cuiar asks before it confirms and pays.

  • 03

    Refill a prescription

    “Refill my allergy prescription on the pharmacy portal, for pickup at the usual branch.”

    Cuiar asks before it submits.

  • 04

    Hear about delays

    openclaw automations create "15 7 * * 1-5" "With Cuiar, check the rail operator's live page for the 07:42 train. Tell me only if it is late or cancelled." --name train --session isolated

    Then send it to Telegram with openclaw automations edit <id> --announce --channel telegram.

  • 05

    Top up a transit card

    “Top up my transit card with 20 EUR if the balance is under 10 EUR.”

    Cuiar asks before it pays with the saved card.

Good to know

Two approvals
OpenClaw's exec approvals can ask in chat with /approve <id>. The Cuiar agent asks before payments and submits.
Your computer
The Cuiar app must be open and signed in. The tabs open there, whatever machine runs the gateway.

Templates to run from OpenClaw

All templates

Each template page shows the run_task or create_routine call to give OpenClaw.

More agents

All AI agents

Start on the Free plan.

The MCP server, the vault and unlimited routines are free. Steps that your own agent takes use no Cuiar credits.

Get CuiarDeveloper docs