f8a9b06323
The universal molecule-mcp wheel is the recommended path for any
MCP-aware runtime — Claude Code, hermes-agent, OpenCode, Cursor, Cline,
custom MCP clients — to join the canvas as a first-class external
workspace. Until now this path had no docs page; users either inferred
it from internal PRs or got pointed at external-agents.mdx (the manual
HTTP+heartbeat path that pre-dates the wheel).
New runtime-mcp.mdx covers:
* Single install (pip install --user molecule-ai-workspace-runtime)
* Per-runtime config snippets (Claude Code, Hermes, generic JSON,
Cursor/Cline)
* Tool surface (delegate_task, wait_for_message, inbox_peek/pop,
send_message_to_user, commit_memory/recall_memory)
* Heartbeat/lifecycle behaviour and the new escalation message
landed in molecule-core PR #2425
* When to use this vs. the manual external-agents path
* Troubleshooting: stale MCP cache, 401 register failure, PATH issues
Cross-links:
* external-agents.mdx now leads with a Callout pointing MCP-runtime
users at the new page; keeps the manual path for non-MCP agents
* meta.json registers the new page under the main docs nav between
schedules and external-agents (related onboarding flow)
Build verified: `npm run build` generates 106 pages including the new
/docs/runtime-mcp.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
33 lines
625 B
JSON
33 lines
625 B
JSON
{
|
|
"title": "Documentation",
|
|
"pages": [
|
|
"index",
|
|
"changelog",
|
|
"quickstart",
|
|
"concepts",
|
|
"workspace-config",
|
|
"architecture",
|
|
"org-template",
|
|
"plugins",
|
|
"channels",
|
|
"schedules",
|
|
"runtime-mcp",
|
|
"external-agents",
|
|
"tokens",
|
|
"api-reference",
|
|
"mcp-server",
|
|
"self-hosting",
|
|
"self-hosting/admin-token",
|
|
"observability",
|
|
"troubleshooting",
|
|
"---Security---",
|
|
"security/index",
|
|
"security/safe-mcp-advisory",
|
|
"security/owasp-agentic-top-10",
|
|
"---Runtimes---",
|
|
"google-adk",
|
|
"hermes",
|
|
"---Integrations---",
|
|
"opencode"
|
|
]
|
|
} |