Tools

The server exposes one fixed MCP bridge surface. It does not generate one MCP tool per registered capability.

Read by task

Task	Start here
See which clients are online	listClients
See the canonical path catalog	listPaths
Invoke one exact path on one exact client	callPath
Fan out one path invocation to multiple clients	callPaths

Discovery tools

Tool	Returns	Notes
listClients	Connected client summaries and connection metadata	Supports case-insensitive search across client fields and catalog
listPaths	Canonical indexed path descriptors	Supports clientId, search, and depth; default depth is one

Invocation tools

Tool	Use when
callPath	You know one client ID plus one exact method + path
callPaths	You want canonical fan-out by method + path

These four tools are the complete canonical bridge surface.

auth is forwarded to the client as callClient.auth:

{
  "scheme": "Bearer",
  "token": "client-session-token",
  "headers": {
    "x-mdp-auth-tenant": "demo"
  },
  "metadata": {
    "role": "operator"
  }
}

Legacy invocation aliases continue to accept args plus optional auth.

Direct HTTP skill reads

Skill documents can also be read directly over HTTP:

curl 'http://127.0.0.1:47372/skills/client-01/workspace/review'
curl 'http://127.0.0.1:47372/client-01/skills/workspace/review/files?topic=mdp'

Those routes resolve one exact skill node and return the skill body directly, commonly as text/markdown.