Clanker CloudA handoff should tell the next person what is ready, what remains unresolved, and where to find the evidence. Hermes can help prepare that handoff using a Clanker Workspace Project through the remote MCP connection.
The working arrangement is simple: Hermes supplies the assistant, while Workspace holds the accessible files and saved outputs. You control the connection's permissions and can inspect the result in your browser.
Add the remote MCP server
Start with a current Hermes client and an existing Clanker account. Add the following entry to your Hermes MCP configuration, preserving other configured servers:
mcp_servers:
clanker:
url: "https://workspace.clankercloud.ai/mcp"
auth: oauth
Then start browser authorization:
hermes mcp login clanker
Review the client and requested permissions on the Workspace consent screen. Select only the access needed for the first job. Restart the relevant Hermes session or use its documented MCP reload controls when needed to expose the connection. Consult Hermes's current MCP guide for your client version and remote-host login arrangements.
The Workspace connection guide describes the permission scopes. A configured URL or tool listing is a starting check; an actual read of the intended file is the useful connection test.
Give the handoff a source packet
Use a fictional Project containing an approved brief, recent notes, and a source register identifying the current versions. Imagine that one note says the customer expects delivery next Tuesday, while another says the delivery date is awaiting confirmation.
Ask Hermes:
Read the current brief, notes, and source register in my Cedar Handoff Project. Prepare a handoff summary with the goal, agreed scope, completed work, unresolved decisions, and next steps. Cite each source. Flag conflicting delivery statements. Do not edit files or contact anyone.
Start with Read access. A useful result preserves the conflict instead of choosing whichever date makes the handoff look complete. It should distinguish a source it actually read from a filename merely mentioned in the notes.
The project handoff template provides fictional inputs and a review checklist for this kind of task.
Save the handoff after checking it
Once the summary is accurate, authorize Edit access if you want Hermes to save it. Existing access does not automatically expand when the prompt asks for a write.
Request handoff-review.md in the same Project, with a source map and open questions. Have Hermes read an existing file before changing it. Open the saved result in Workspace and check that the unresolved delivery date is still visible.
A file can be used by another permitted assistant or colleague through the relevant access path. The MCP connection does not automatically transfer Hermes's private memory, previous conversations, or model settings into Workspace. Save the project facts that the next person or Agent actually needs.
Keep connection and hosting separate
Hermes connected by MCP continues to run through your Hermes client. A Hermes BYOA registration is a separate setup for a supported runtime and Project. Follow the BYOA guide when that is the arrangement you want.
Regular Workspace recurrence and managed email do not run native BYOA harnesses. For a weekly handoff, create a tested hosted Workspace Agent and configure a Schedule. For an incoming request, use the managed Agent email workflow.
Hermes's independent model usage stays with its provider; Clanker-hosted work uses the authorizing user's Clanker credits. Manage and revoke the Workspace connection at agent-connect, and review usage costs before adding compute or recurring work.
Sources
Give your assistant one useful job
Give your Hermes assistant approved access to project tools and keep a useful handoff with the source files.