From fa6db57daf9b4d579ca3e14e3a5c9b196cd3ac4f Mon Sep 17 00:00:00 2001 From: Hongming Wang Date: Thu, 30 Apr 2026 19:00:44 -0700 Subject: [PATCH] docs(runtime-mcp): document MOLECULE_AGENT_NAME / DESCRIPTION / SKILLS MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Adds an "Optional — declare your identity & capabilities" section to the Bring Your Own Runtime page covering the three new env vars landing in molecule-core PR #2428: * MOLECULE_AGENT_NAME — display name on canvas card * MOLECULE_AGENT_DESCRIPTION — one-liner in Details/Skills tabs * MOLECULE_AGENT_SKILLS — comma-separated skills Includes a worked example for Claude Code's add command and explains the two surfaces these populate (canvas Skills tab, peer agents' list_peers output) so readers understand why declaring skills matters for routing. Co-Authored-By: Claude Opus 4.7 (1M context) --- content/docs/runtime-mcp.mdx | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/content/docs/runtime-mcp.mdx b/content/docs/runtime-mcp.mdx index c6e5d9d..bfca8fd 100644 --- a/content/docs/runtime-mcp.mdx +++ b/content/docs/runtime-mcp.mdx @@ -102,6 +102,40 @@ example above. Drop it into your client's MCP settings file (typically `~/.cursor/mcp.json` for Cursor, the MCP Servers panel for Cline) and restart the client. +## Optional — declare your identity & capabilities + +Three additional env vars control how your workspace appears on the +canvas and to peer agents calling `list_peers`: + +| Env var | What it sets | Default | +|---|---|---| +| `MOLECULE_AGENT_NAME` | Display name on the canvas card | `molecule-mcp-{id[:8]}` | +| `MOLECULE_AGENT_DESCRIPTION` | One-line description in Details/Skills tabs | empty | +| `MOLECULE_AGENT_SKILLS` | Comma-separated skill names — e.g. `research,code-review,memory-curation` | `[]` | + +Skills are surfaced two places: + +1. **Canvas Skills tab** — each skill renders as a chip with the name +2. **Peer agents calling `list_peers`** — they see `{name, skills: [...]}` for each peer, so other agents can route delegations to the right specialist instead of guessing from name alone + +Example with all three set: + +```bash +claude mcp add molecule -s user -- env \ + WORKSPACE_ID= \ + PLATFORM_URL=https://.moleculesai.app \ + MOLECULE_WORKSPACE_TOKEN= \ + MOLECULE_AGENT_NAME='Research Assistant' \ + MOLECULE_AGENT_DESCRIPTION='Reads, summarises, cites.' \ + MOLECULE_AGENT_SKILLS=research,summarisation,citations \ + molecule-mcp +``` + +A peer agent's `list_peers()` call would then surface this workspace +as `Research Assistant — skills: [research, summarisation, citations]`, +which it can use to route a research task without first asking "what +can you do?". + ## Step 3 — Verify After your runtime reconnects, the workspace should flip to **online**