Clanker CloudClaude can work with files you paste into a conversation. A Workspace connection gives it another route: use approved tools to find a Project, read its files, and save work back where you can inspect it.
Clanker Cloud's remote MCP address is:
https://workspace.clankercloud.ai/mcp
MCP is the connection protocol. Claude supplies the assistant; Clanker Workspace supplies the permitted project tools and storage. Your Claude account and your Clanker account remain separate.
For the complete Project workflow, use the dedicated Claude Workspace guide. It includes a copyable prompt, a saved decision pack, and a handoff you can reuse in another conversation.
Add the connector and authorize access
Sign in to Clanker Workspace first. Prepare a small Project with fictional or non-sensitive sample files so you can check the connection on work you understand.
In Claude, open Customize → Connectors and use the option to add a custom connector. Give it a recognizable name, enter the MCP address above, and follow its authentication setup. Complete the browser sign-in to Clanker and inspect the requested permissions before approving them. Enable the connector for the Claude conversation where you want to use it.
Claude's menu labels and connector availability can vary with the account and organization. Team or Enterprise members may need an owner to add the connector first. Follow Anthropic's current connector instructions if the controls differ.
Remote connectors are reached from Anthropic's infrastructure. This Workspace address is the hosted connection; a local desktop MCP endpoint is a different setup.
Begin with one read-only job
Create a fictional Project called Cedar Launch Review. Add a brief and a scope checklist, then ask Claude:
Use my Clanker Workspace connection to find Cedar Launch Review. Read the brief and scope checklist. Return a table showing each requested deliverable, its supporting source, and any missing scope detail. Do not modify files or send messages.
Read permission is enough for this first check. Verify that Claude found the intended Project, read the actual files, and distinguished a confirmed requirement from an assumption. If the brief omits a deadline, a useful result says the date is missing.
Do not evaluate the connection only by whether a tool appears in a menu. Check the content it returns. If a file is read in parts, the agent should retrieve the remaining content before describing the whole document as reviewed.
Save the result when you are ready
Saving or editing files requires Edit access. Configuring Agents or running hosted commands requires the corresponding execution access as well. The permission guide explains the available scopes; an existing connection does not automatically acquire extra ones.
Before writing, have Claude read the current managed Session instructions. It should start a visible task Session, retain its sessionId for changes, record public progress, read back saved files, and complete the task. The external conversation is not copied automatically; save the context the next task should use.
After approving the necessary access, ask:
Follow the live managed Session workflow before making changes. Save the reviewed scope table as launch-scope-review.md in Cedar Launch Review. Include the source filenames and the unresolved deadline question. If that file already exists, read its current contents before proposing an update. Tell me where the result was saved.
Open the file in Workspace. Compare the table with the original brief and check that the report exists in the intended Project. A completion message alone is not the deliverable.
When an operation has an uncertain outcome, inspect the file or job before asking the assistant to repeat it. This matters for edits and commands, where a second attempt could duplicate work.
Understand what the connection enables
Granted permissions can cover the connected user's accessible Workspace, including shared Projects within their existing role. Naming a Project in the prompt does not narrow the authorization to that Project. Review the scope on the consent screen and manage connections at agent-connect.
Claude's own model usage stays with its provider. Clanker-hosted work and compute use Clanker credits. Merely reading a file or saving a Session message does not start a separate Clanker model conversation.
This connector also does not schedule future work automatically. To turn the review into a recurring business task, create and test a hosted Workspace Agent, then configure a Schedule or Loop. If you want Claude Code as a registered runtime inside Workspace, follow the separate BYOA setup described in the agent workspace overview.
Sources
Give your assistant one useful job
Connect your Claude assistant to Workspace, begin with a small file review, and inspect the work in your Project.