Clanker WorkspaceOpen Workspace Your assistant. Your Workspace.
Connect the assistant you already use to Clanker Cloud: a persistent agent workspace, an environment for work, and an agent factory. Follow the setup below, starting with read access.
No Clanker API key · No desktop installation · Guide updated October 19, 2026
One server URL for both
https://workspace.clankercloud.ai/mcpChoose OAuth. Sign in or create your Clanker account in the browser, check the client and callback, and approve the access you want. Read is selected by default. Write, execution, and plan checkout are separate permissions.
A few steps, then you’re connected
Controls and availability vary with client version and organization policy. Ask your administrator if custom connectors or plugins are unavailable. This is a custom connection you add to your own account.
Check before doing work
With the connector enabled in your conversation, send this prompt. The test checks status and permissions without reading your project content.
Use my Clanker Cloud Workspace connection. Call workspace_status once and report whether the connection is working and which permissions are granted. Do not read project content, change anything, run tools that execute work, or request additional permissions.A successful workspace_status response confirms the connection. It does not confirm that every provider, paid action, or execution capability is available. Next, choose a Project and ask for a task using approved material.
Go further when the task needs it
Projects, files, Sessions, Planner, knowledge, Word documents, spreadsheets, and slides.
Create specialist Agents, add Skills and reusable Tools, and configure schedules and automations.
Use hosted compute, cloud browser and desktop, Apps, builds, and supported media generation.
Use channels and connected apps within the service access and permissions you approve.
The full connection exposes 46 MCP tools, including workspace_search_tools and three native invokers. The searchable catalog has 160 native definitions, with 159 remotely eligible actions. Local-tab control needs a separately granted browser-extension tab. Available actions depend on permissions, account features, and provider access.
Read Workspace resources within your existing role. Start here for the connection test.
Create, update, and delete saved work when you want the assistant to save a deliverable.
Configure Agents and tools, run compute and browser work, and start builds or automations. Also requires write access; can consume credits or affect external services.
Optional subscription status and plan checkout. Review and confirm payment in Stripe. Preparing checkout does not buy a plan.
Access covers the resources available to your Workspace role. Naming a Project in chat does not narrow the OAuth grant to that Project. Connections expire after 30 days. Existing grants never expand automatically.
Open External agents or Settings → External agents to review or disconnect a connection. Work already queued may continue and can be stopped separately.
In Customize → Connectors, open Manage your connectors and the connector’s menu, then Refresh tools list. Start a new conversation and enable the connector again.
Open the Workspace plugin’s connection settings and refresh its tools (Refresh or Refresh tools). Verify the updated metadata, then select the plugin in a new conversation.
The current MCP surface is 3.0.0. Older execution grants retain their original limits. Reconnect and review the current execution permission when newly added actions are needed; keep the status test read-only.
Check that you used the full HTTPS /mcp URL, selected OAuth, and signed in to the intended Clanker account. Organization policy may restrict custom connections. A public page or pasted prompt does not grant access to a private Workspace. Never paste a password, cookie, API key, or recovery code into chat.
The smaller https://workspace.clankercloud.ai/mcp/workspace connector offers eight read tools and ten optional write tools for saved work and disabled Agent drafts. It cannot execute Agents, run commands, send messages, generate media, schedule work, or access billing.
Read the OpenClaw, Hermes, and other client guide. Terminal agents use the separate browser-approved HTTP login workflow. Account cookies and OAuth tokens are separate credentials and cannot be interchanged.
Instructions for the assistant
workspace_status to test access. Search workspace_search_tools for the task and use the returned schema with the matching read, write, or execution invoker.sessionId and stable idempotencyKey to changes. Keep public progress updated, inspect saved files and job receipts, and complete the Session.Create an account or sign in, then connect your assistant using this guide.
Sign in and manage connections →