From e1fecc240c1e3e0b0d400f2f01c12291d3f2aacd Mon Sep 17 00:00:00 2001 From: Madraka <8898640+Madraka@users.noreply.github.com> Date: Wed, 21 Oct 2026 11:57:02 +0300 Subject: [PATCH] docs(agents): say Bearer keys need a 0.3.4 deployment Co-Authored-By: Claude Opus 5.5 Signed-off-by: Madraka <8898640+Madraka@users.noreply.github.com> --- docs/agents/clients.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/agents/clients.md b/docs/agents/clients.md index 8def7a7d..5bc13d3d 100644 --- a/docs/agents/clients.md +++ b/docs/agents/clients.md @@ -3,7 +3,7 @@ Every MCP client connects to Cloudhal in one of two ways ([which one?](/docs/agents#two-ways-to-connect)): - **Local server:** the client starts `cloudhal mcp` in your project folder. Nothing to authenticate; the agent works on the project's local store. -- **Remote server:** the client calls `https:///mcp` on a deployment, sending an agent key created in Studio under **Agents** as `Authorization: Bearer ` or in the `x-api-key` header. Both work; use whichever your client supports. Studio shows each client's setup with the key filled in right after you create it. +- **Remote server:** the client calls `https:///mcp` on a deployment, sending an agent key created in Studio under **Agents** as `Authorization: Bearer ` or in the `x-api-key` header. Both work; use whichever your client supports. Bearer needs a deployment on Cloudhal 0.3.4 or later; on older ones use `x-api-key`, or upgrade and run `cloudhal deploy`. Studio shows each client's setup with the key filled in right after you create it. `cloudhal mcp` serves the project folder it starts in. Configure local servers **per project** (the project-scoped files below), or start the client from the project folder.