v0.10.0

Full Changelog: v0.9.0...v0.10.0

v0.9.0

What's Changed

• Correct managed MCP service port assignments by @Wixely in #10

Full Changelog: v0.8.0...v0.9.0

v0.8.0

Agents can now manage the servers MCPHub runs

Until now an agent that needed Kodi's tools while Kodi's server was stopped could only report them missing. Agents connected to the proxy can now operate the managed servers themselves through mcphub__* tools — off by default, and switched on under Settings → Agent management.

Tool	Does
mcphub__list_services	Every managed server with its install state, versions, run state and port
mcphub__start / stop / restart	Drive a server and wait for it to report healthy (wait_seconds, default 30)
mcphub__install	Install a server that is not installed, from its latest GitHub release; start: true brings it up
mcphub__update	Check for a newer release and install it, preserving config and restarting the server if it was running; force: true reinstalls
mcphub__check_service_updates	Check GitHub for one server or all of them, installing nothing
mcphub__check_hub_update	Compare the running MCPHub with its newest release — MCPHub never replaces itself, so the agent is told to hand you the release page URL

• Gated in layers. One master switch grants mcphub__list_services; three capability switches beneath it grant control (start/stop/restart), install/update, and update checks. They persist as soon as they are toggled and are enforced as proxy tool authorization, so a disabled tool vanishes from the tool list and is refused on call immediately — no restart.
• Headless overrides. MCPHUB_AGENT_MANAGEMENT_ENABLED, _CONTROL, _INSTALL and _UPDATE_CHECKS pin each switch from the environment (true/false, 1/0, yes/no, on/off); the Settings page shows a pinned checkbox locked and names the variable.
• Config and logs stay yours. No tool reads or returns a server's config files, install paths or logs. If a server will not start, the agent is told to ask you.
• Servers are addressed by proxy key (kodi), product name (KodiMCPSharp) or display name. Operations on one server are serialised, and every agent-driven action is written to that server's log so the Logs page shows who did what. The proxy's MCP instructions describe the granted capabilities on connect, so an agent knows it can start a stopped server instead of giving up.
• For embedders, MCPHub.Proxy gains CompositeToolAuthorization for stacking independent feature policies in front of one ProxyHandlers, and IServiceManager raises ServiceChanged so a UI can follow changes an agent makes.

222 tests pass (25 new, including an end-to-end MCP-over-HTTP run); the solution builds with no warnings.

Full Changelog: v0.7.0...v0.8.0

v0.7.0

Recipes — a knowledge base agents and users share

Some tasks need two servers that know nothing about each other: Kodi's tools are useless until Kodi is running, but ADB can launch it on Android and Remote Admin can start it on a Windows or Linux box. Recipes give agents somewhere to keep that kind of "if X then Y" note, so the next session doesn't have to rediscover it.

• Agents reach recipes through the proxy as recipes__list / get / add / update / remove, and the hub sends server instructions on connect so agents know to consult them before a multi-server task or when a tool fails because a dependency isn't running.
• A new Recipes page searches, adds, edits and deletes notes, refreshing live when an agent writes. Recipes are stored in recipes.json beside settings.json with atomic writes, tight size limits, and quarantine of a corrupt file.
• Two switches control agent access: Let agents use recipes and Let agents add and edit recipes — enforced as proxy tool authorization, so they apply immediately. MCPHUB_RECIPES_ENABLED / MCPHUB_RECIPES_AGENT_EDIT override them for headless deployments.
• For embedders, MCPHub.Proxy gains ILocalToolProvider (hub-native tools advertised, routed, authorized and audited like an upstream's) and MCPHub.Hosting gains ProxyHostOptions.ServerInstructions.

Three new catalogue servers

ADBMCPSharp, KodiMCPSharp and BambuMCPSharp, each verified against its repo config and release zip contents. Note: KodiMCPSharp's default port (5712) currently collides with the SQL server's — change it in Settings if you run both; a new default has been requested upstream.

Fixes and improvements

• An unwritable data directory was previously reported as "MCPHub is already running" (exit 2, no window). MCPHub now tells the two apart and starts unguarded with a warning naming the path.
• The Updates page has an Open install folder button that opens the running executable's folder, ready for swapping in a downloaded build.
• MCPHub refuses to start a second instance unless explicitly asked to (--allow-multiple-instances).

192 tests pass in Release; the solution builds with no warnings.

What's Changed

• Refuse to start a second instance unless asked to by @Wixely in #8
• Recipes knowledge base, three new catalogue servers, v0.7.0 by @Wixely in #9

Full Changelog: v0.6.0...v0.7.0

v0.6.0

Full Changelog: v0.5.0...v0.6.0

v0.5.0

What's Changed

• Add PortainerMCPSharp to the catalog and correct two stale ports by @Wixely in #1
• Read every server's port from its own config instead of hard-coding it by @Wixely in #6
• Give multi-config services a Config dropdown that creates files from templates by @Wixely in #5
• Turn Start into Restart once a service is running by @Wixely in #4
• Add a name search box to the services list by @Wixely in #2
• Add a user-facing README by @Wixely in #3
• Refresh the screenshots against the current UI by @Wixely in #7

New Contributors

• @Wixely made their first contribution in #1

Full Changelog: v0.4.4...v0.5.0

v0.4.4

Full Changelog: v0.4.3...v0.4.4

v0.4.3

Full Changelog: v0.4.2...v0.4.3

v0.4.2

Full Changelog: v0.4.1...v0.4.2

v0.4.1

Full Changelog: v0.4.0...v0.4.1