The point is not a capability of its own — it is that the server list and its settings live in the Resource Hub, so a new machine or a teammate arrives at the same setup by holding a token. What shows up in your client therefore depends entirely on how that Hub is configured, and the Hub owns whatever credentials those servers need.
A proxy between your local MCP environment and the Resource Hub, a hosted place where MCP server configuration lives. The client talks to this one server; what it can actually reach is decided centrally rather than by the config file on the machine.
- The tools and resources configured on your Resource Hub, reaching a local client through a single connection
- One configuration shared across environments, so a second machine is a token rather than a copied config file
- Server settings changed in one place instead of in every client that uses them
A Resource Hub token, taken from the Resource Hub token page and passed as RESOURCE_HUB_TOKEN — it is the only environment variable and it is required. Run it with `npx @adamwattis/resource-hub-server`, version 0.1.0; from source it is `npm install`, `npm run build`, then `npm start` with the same variable set.
One command plus a key — npx @adamwattis/resource-hub-server, then supply credentials