Keep your assistant.
Give it a cloud workspace.

Choose your assistant.

Controls and availability can vary with client version and organization policy. These instructions describe a custom connection you add to your account. Ask your administrator if custom connectors or plugins are unavailable.

A small first step

Check the connection before doing work.

Enable the connector in your conversation and send this prompt. The first test checks status and permissions, without opening your project content.

A successful workspace_status response confirms the connection. It does not confirm that every provider, paid action, or execution capability is available. After testing, select a Project and ask for a specific task using material you approve.

A space to work. A runtime when you need it.

Keep context in a Project, carry out a visible task, and save a result someone can inspect. Choose the layer your work needs.

Connecting an external assistant gives it authorized Workspace tools. Hosting its agent process is a separate choice; a saved Project does not keep a machine running.

A workspace. An environment. An agent factory.

Use the connection to keep work across conversations, create specialist Agents, prepare Office files, run compute, browse, and automate tasks. Discover the tools for each task instead of guessing their names or arguments.

The current full connection exposes 46 MCP tools, including workspace_search_tools and three native invokers. The searchable catalog contains 160 native definitions, with 159 remotely eligible actions. Local-tab control needs a separate browser-extension grant. Actions depend on account features, permissions, and provider access.

Inspect the current tool catalog · What is an agent workspace? · What is an agent factory?

You choose the access.

The grant covers accessible Workspace resources within your role; naming a Project in chat does not narrow that grant to one Project. Existing connections never gain new permissions automatically. Disconnect in Settings → External agents or manage connections. Connections expire after 30 days; work already queued may continue.

Connected, but seeing old tools?

The current MCP surface is version 3.0.0. Older execution grants retain their original limits. Reconnect and review the current execution description when your task needs newly added actions. Keep a status-only test read-only.

If sign-in fails, confirm the full /mcp URL, OAuth selection, browser account, and organization policy. A public page or pasted prompt cannot authorize private Workspace access. For a smaller saved-work-only connector, use https://workspace.clankercloud.ai/mcp/workspace; it offers read and optional write access without execution or billing.

Instructions for the assistant

Read the runbook. Then do the task.

1. Read the MCP runbook and Workspace-hosted agent instructions. Guide the owner through the client’s OAuth setup if the connection is missing. Keep passwords, cookies, and recovery codes out of chat.
2. Test with workspace_status. Search workspace_search_tools for the requested task, then use the appropriate read, write, or execution invoker with the returned schema.
3. Before changes, start a managed Session. Pass its sessionId and a stable idempotencyKey to changes, keep public progress updated, inspect saved results and job receipts, then complete the Session.
4. Stop after takeover, revocation, or completion. A queued build is not a published App. Do not retry uncertain side effects with a new key or request broader access without an owner-authorized task.

Read this guide on Workspace · HTTP API reference

Bring another compatible agent.

{
  "mcpServers": {
    "clanker": {
      "httpUrl": "https://workspace.clankercloud.ai/mcp",
      "oauth": {
        "enabled": true,
        "scopes": [
          "workspace:read"
        ]
      }
    }
  }
}

openclaw mcp set clanker '{"url":"https://workspace.clankercloud.ai/mcp","transport":"streamable-http","auth":"oauth","oauth":{"scope":"workspace:read"}}'
openclaw mcp login clanker

mcp_servers:
  clanker:
    url: "https://workspace.clankercloud.ai/mcp"
    auth: oauth

Other clients need Streamable HTTP MCP and OAuth with PKCE. Agents with a terminal can use the separate browser-approved HTTP login workflow. The hosted MCP connection does not require Clanker Desktop; desktop setup is separate.

A few things to know.