Devframe

DF8005: Devframe MCP Ignored While Hub MCP Is Off

Devframe "{id}" requests an MCP route, but the hub's aggregate MCP is off (`mcp: false`), so its tools are not exposed over MCP.

Message

Devframe "{id}" requests an MCP route, but the hub's aggregate MCP is off (mcp: false), so its tools are not exposed over MCP.

Cause

A hub exposes one aggregate MCP endpoint over every mounted devframe (tool ids are already namespaced per plugin), so a mounted devframe's own mcp setting is ignored: the hub's own mcp governs the route. This warning fires when a mounted devframe's definition enables MCP through the deprecated cli.mcp field while the hub set mcp: false, so that devframe's tools are not reachable over MCP.

Example

The hub below turned MCP off, but a mounted devframe's definition requests MCP:

initHub({
  base: DEVFRAMES_HUB_BASE,
  mcp: false,
  devframes: [myDevframe], // myDevframe's definition requests MCP, so DF8005
})

Fix

  • Drop mcp: false from initHub: the 'auto' default mounts the aggregate route once agent tools exist, and mcp: true / mcp: { authorization } force or harden it.
  • Or drop mcp from the mounted devframe to silence the warning; it has no effect inside a hub.

Source

DF8004: Devframe Id Is Not a Mountable URL Segment

Devframe id "{id}" is not a mountable URL segment; the hub mounts each frame at <base><id>/.

DF8100: Dock Already Registered

Dock with id "{id}" is already registered