03 · Python · MCP · fyos-hub 0.1.3 · PyPI
MCP-Hub
One MCP server, many plugins: every capability built once and usable everywhere.
- tools in 10 plugins in the base install
- 34
- tools in 73 plugins in our own deployment
- 288
- access paths: MCP, REST and shell
- 3
What it is
The hub bundles tools and interfaces from plugins under one address. Agents and chat clients speak MCP at /mcp, the shell and scripts speak REST at /hub/*. Whatever a plugin registers once is available in the agent, in the shell, in any MCP client and in scripts – with the same interface.
What it does
- Federated. The model sees a few meta-tools – search, read schema, call – instead of every single tool in its context.
- Plugins by entry point. Installing a Python package with
mcp_hub.pluginsis enough; configuration is only needed for settings and secrets. - Apps with an interface. Tools bring their interface as
ui://HTML; the shell and chat clients with MCP Apps support render it. - Short view. Large results come back shortened with a result ID and can be drilled into on demand – that saves tokens.
- Included. Skills, a workshop (registered scripts with dry runs), an audit log with vector search, an event bus and shell control.
- Every protocol revision. From the 2024-11-05 handshake to the stateless 2026-07-28 revision.
Screenshots
Captured on the distribution’s neutral test server (October 2026), no personal data. Click to enlarge.
Get started
$ pip install "fyos-hub[suche]"
$ fyos-hub # MCP /mcp · REST /hub/* · /health