Clanker CloudA practical Workspace guide
Bring Meta’s Muse Code into your workflow.
Connect Meta’s Muse Code agent to Clanker Cloud so it can work with approved Project context and save results beside your team’s work. Muse Code is the agent client; Muse Spark is its model family. This connection uses the client’s documented remote MCP and OAuth support, rather than assuming the Meta AI consumer chat has the same features.
Start with $20 in included credits. See usage and plans.
Add Workspace to Muse Code
In Muse Code’s settings file, add a server named clanker under mcp_servers with transport set to streamable_http, url set to https://workspace.clankercloud.ai/mcp, enabled set to true and mode set to optional. The documented user settings location is ~/.config/muse/settings.json.
Run muse mcp login clanker and complete browser sign-in. Review the requested permissions in Clanker, starting with Read. In Muse Code, use /mcp to inspect the connected tools. Keep credentials in the client’s authentication storage, not in prompts or source files.
Sources: Meta: Muse Code MCP and OAuth · Meta: Muse Code settings and project context · Workspace connection and permissions
Give the build a business brief
For a client portal, add the approved requirements, a sample data dictionary and brand notes to a Project. Ask Muse Code to read the actual files and save implementation-plan.md with the proposed screens, data requirements, assumptions and questions.
Request acceptance-checklist.md covering the main user journey, empty states and data validation. If the brief does not define login rules or deployment ownership, keep those as open decisions. Planning from a brief is useful before starting a build.
Keep the plan and the code’s location together
Approve Edit for saved deliverables and follow the managed Session instructions. Read back the plan, checklist and handoff in Workspace. If the task also changes a local repository, record the repository and revision in the handoff.
A local file does not appear in Clanker just because Muse Code created it. Save the deliverables through the approved Workspace tools. Building or publishing a private Clanker App needs its own tools and permissions; an implementation plan is not a deployed app.
Sources: Live Workspace instructions for connected agents · Build and review a private App
Let the next agent pick up the right work
After a teammate reviews the plan, an authorized Claude or ChatGPT task can read the same brief and saved handoff to prepare release notes, a user guide or a client update. Give that task the current file versions and the decisions it may rely on.
Use your Workspace group chat to discuss the result with people and Workspace agents. Muse Code’s local sessions, memories and repository instructions remain in their own environment; they are not automatically shared with every agent.
Sources: Agent handoff starter · Shared work across supported assistants
Check the connection before expanding the workflow
Meta documents the client’s MCP and OAuth features. This guide does not claim an authenticated Muse Code-to-Clanker business run or an official Meta integration listing. Verify status, one approved source read and one saved-file readback on your installed version.
Your Muse provider account and Clanker usage are separate. Remote MCP connects tools; it does not automatically host Muse Code in Clanker, copy its full history, or activate a recurring worker.
Before you use the result.
- Muse Code lists the Workspace tools and reports the intended account permissions.
- The plan reflects the approved brief and preserves unanswered questions.
- The saved files open in Workspace and identify any separate code revision.
- The next agent reads the saved handoff rather than assuming shared memory.
Common questions.
Which Muse does this guide cover?
Meta’s Muse Code agent, powered by the Muse Spark model family. It does not cover unrelated products named Muse or promise the same MCP setup in the Meta AI consumer app.
Does this select Muse Spark as a model inside Clanker?
No. It connects an external Muse Code client to permitted Workspace tools. Model selection inside Clanker depends on the models actually available in your account.
Where does the work stay?
Files successfully saved through Workspace tools stay with the selected Clanker Project. Local code and Muse Code session state remain in their own locations unless explicitly saved or linked in the handoff.
Sources: Workspace connection and permissions · Live Workspace instructions for connected agents · Meta: Muse Code MCP and OAuth · Meta: Muse Code settings and project context
Content reviewed against the Workspace Guide & FAQ. Features and access can depend on your account.