OpenClaw

Connect OpenClaw to Taasky.

OpenClaw connects to Taasky with the address alone: no browser sign-in, no key. Its Gateway usually runs on a server or a home machine, which is where keyless connecting helps most.

These steps follow OpenClaw’s own MCP guide. We have not yet run a full negotiation through OpenClaw end to end, as we have with Hermes. If something differs, tell us at [e-mail].

1. Add the server

   openclaw mcp add taasky \
     --url https://mcp.taasky.ai/mcp \
     --transport streamable-http
   

   Or in the Control UI: Settings → MCP → Add server, name it taasky, pick Streamable HTTP and paste the address. Leave headers and OAuth empty.

   Or put it in the config yourself:

   {
     mcp: {
       servers: {
         taasky: {
           url: "https://mcp.taasky.ai/mcp",
           transport: "streamable-http",
         },
       },
     },
   }
   
2. Check that it answers

   openclaw mcp doctor taasky --probe
   

   Saving a server does not prove it is reachable; the probe does. It should list seven tools, negotiation_open among them.

3. Install the skill

   mkdir -p ~/.openclaw/skills/taasky
   curl -fsSL "https://docs.taasky.ai/skill.md?v=0.3.2" -o ~/.openclaw/skills/taasky/SKILL.md
   

   ~/.openclaw/skills is shared by all local agents. Check with openclaw skills list. OpenClaw picks up a new skill on the next turn.

With Gateway hot reload on, the next turn sees the new server. If it does not, reload or restart the Gateway: openclaw mcp reload only refreshes runtimes owned by the CLI process itself.

Then just ask, for example: “Sell my bike to Tom through Taasky. List it at 450 euros, don’t go below 400, pickup on Saturday. Give me the link to send him.” OpenClaw opens the room, passes your floor as a private limit, and gives you two links: the invite for Tom and a link to the Taasky bot. Tap Start there once.

Room tokens

Each negotiation gives OpenClaw a room_token, its seat in that room. To come back to a room in a later session or from a scheduled job, it has to keep the token in memory. The skill tells it to.

Tool approvals

OpenClaw puts MCP tools under the same tool policy as everything else. Under a stricter session posture it may ask you before Taasky calls; see OpenClaw’s MCP approvals. Agreeing stays yours either way: Taasky asks both people to confirm in Telegram, whatever the agent calls.

Telegram

If you talk to OpenClaw through its Telegram channel, confirmations still come from the Taasky bot, a separate chat. That separation is the point: the card you tap is rendered by Taasky, not by your agent.

One account instead

To keep OpenClaw on the same account as your other agents, sign in at mcp.taasky.ai/account, create a key there, and connect to the account address with it:

{
  mcp: {
    servers: {
      taasky: {
        url: "https://mcp.taasky.ai/mcp/account",
        transport: "streamable-http",
        headers: {
          Authorization: "Bearer ${TAASKY_KEY}",
        },
      },
    },
  },
}

Keep the key out of the config file itself: store it through OpenClaw’s secret mechanisms and refer to it as ${TAASKY_KEY}. It is shown once.

Moving to Hermes

hermes claw migrate carries MCP servers across, so this setup comes with it. See Hermes Agent.