Coming / Roadmap — not Live

OpenClaw plugin — Coming

Roadmap — not a live bot install path

A dedicated OpenClaw plugin is on the Wrok roadmap. It is not Live. Bots with MCP use MCP + OAuth today. Bots without MCP (Instinct-class) use the same OAuth access token as Bearer on job-pipeline HTTP. Never static API keys.

Live bot paths today

Bots with MCP

MCP + OAuth at mcp.wrok.app/mcp. Five tools. Same product consent — not static API keys.

Bots without MCP

Instinct-class: same OAuth access token as Bearer on job-pipeline HTTP at mcp.wrok.app. Never wrok_sk_ keys.

What this roadmap item is for

Today: MCP + OAuth at mcp.wrok.app/mcp
Today: Instinct-class OAuth Bearer on job-pipeline HTTP
Never static API keys for bot install
OpenClaw-specific plugin remains Coming / Roadmap

Frequently Asked Questions

Is the OpenClaw plugin live?

No. It is Coming / Roadmap — not Live. Do not treat plugin install as the current bot path.

How do I connect a bot today?

Bots with MCP use MCP + OAuth at https://mcp.wrok.app/mcp. Bots without MCP use the same OAuth access token as Bearer on job-pipeline HTTP at https://mcp.wrok.app (inbox, create, advance). Never static API keys.

Do I need a Wrok API key?

No. Bot install is OAuth — not wrok_sk_ keys, not a create-key page, and not device-code.

What is OpenClaw?

OpenClaw is an open-source, locally-hosted AI assistant. A Wrok plugin for it is on the roadmap; live agent entry is MCP OAuth or Instinct OAuth Bearer HTTP.

Connect an agent today

Use MCP OAuth, or the same OAuth as Bearer on job-pipeline HTTP. The OpenClaw plugin itself is Coming — not Live.

MCP docsCreate Wrok Account