Summary

The tool list is a configuration decision, not a package version.

The point of this connector is that what the assistant can do is decided in Gentoro and can be changed without touching a client config or shipping a release. That is genuinely useful when different people need different subsets — and it means the interesting work is on the Gentoro side, so evaluate the bridge, not this package.

What it is

A thin MCP connector for Gentoro. The tools are not defined here: you assemble them in Gentoro as a bridge, together with the data sources they reach, and this server exposes that bridge to an MCP client. Turning a tool on or off happens in Gentoro, not in your client config.

What you get

Whatever tools your bridge defines — the catalog is controlled per design in Gentoro Studio rather than fixed by this package
The underlying data sources those tools reach, through the same connection
One MCP entry per bridge, addressed by its bridge UID, so different assistants can be pointed at different tool sets

Requirements

A Gentoro account — request one at the Gentoro Playground or install Gentoro locally — a Gentoro API key, and a bridge defined in Gentoro Studio. Run it with `npx -y @gentoro/mcp-nodejs-server` and supply `GENTORO_API_KEY`, `GENTORO_BRIDGE_UID` and `GENTORO_BASE_URL` in the env block, or the single combined `GENTORO_KEY` in the form `<api key>/<bridge uid>/<url>`, which Gentoro Studio generates for you. Package `@gentoro/mcp-nodejs-server` at 0.0.7.

Setup effort

One command plus a key — npx -y @gentoro/mcp-nodejs-server, then supply credentials