dsh-mcphub

If you already use MCPHub to aggregate multiple MCP servers behind a single endpoint but want DSH agents to call those tools directly, dsh-mcphub is built for exactly that. It connects to MCPHub s Streamable HTTP endpoint via the official MCP SDK and registers every discovered tool as a native DSH agent tool. Parameter schemas pass through unchanged and call results are projected back into the model context as MCP text blocks. No extra glue scripts or manual per-server wiring required.

Two built-in agent tools ship with the plugin. mcphub_status reports connection state, endpoint, tool inventory, and health; mcphub_resync forces a tool-set resync after you add, remove, or rename servers or tools on the MCPHub side. A dedicated MCPHub entry sits at the bottom of the sidebar; clicking it opens a status panel where you can browse tools grouped by server, check recent errors, refresh manually, and jump straight to the MCPHub Dashboard. On disconnect the plugin retries with exponential backoff while keeping tools registered; once the connection recovers it auto-resynchronizes. If MCPHub is unreachable the plugin still activates gracefully without blocking other functionality.

This plugin suits users who run MCPHub locally (default localhost:3000) and want unified tool access inside DSH multi-agent sessions. If you only use a single MCP server, dsh-mcp-client may be the lighter choice. When you manage many servers behind one gateway, dsh-mcphub lets agents call every enabled tool in a single conversation without the overhead of registering each server individually.