mcp-nodejs

This MCP server integrates Gentoro tools and data sources with Claude or other agents via a centralized Gentoro bridge. The server is driven by Gentoro's bridge configuration, which can enable or disable individual tools and capabilities from Gentoro Studio. To use it, start the MCP server using the provided npx command so that the server loads the Gentoro tools defined in your bridge and exposes them through the MCP interface. Your agent can then query, invoke, or orchestrate Gentoro tools through the MCP layer, with the actual behavior controlled by Gentoro's bridge settings.

Prerequisites:

• Node.js and npm installed on your machine
• Access to a Gentoro account and a defined Gentoro bridge

Steps:

1. Install Node.js from https://nodejs.org (npm comes bundled with Node.js).
2. Prepare your config.json with the Gentoro MCP server entry as shown below:

{
  "mcpServers": {
    "gentoro": {
      "command": "npx",
      "args": [
        "-y",
        "@gentoro/mcp-nodejs-server"
      ],
      "env": {
        "GENTORO_API_KEY": "<your api key>",
        "GENTORO_BRIDGE_UID": "<your bridge uid>",
        "GENTORO_BASE_URL": "<url where gentoro is hosted>",
        "GENTORO_KEY": "<your api key>/<your bridge uid>/<url where gentoro is hosted>"
      }
    }
  }
}

3. Save the file as config.json in a working directory.
4. Run the MCP server using the command from the config:

npx -y @gentoro/mcp-nodejs-server

5. Verify the server starts and consult Gentoro Studio for enabling/disabling tools within your bridge. Ensure your environment variables are correctly set and accessible to the process.

Tips and notes:

• The server’s capabilities are governed by Gentoro Bridge configuration; you can enable/disable tools without altering the MCP server code.
• If you prefer using a single GENTORO_KEY, you can provide the shorthand syntax described by Gentoro (GENTORO_KEY combines API key, bridge UID, and base URL).
• Ensure network access to Gentoro services and that the provided GENTORO_BASE_URL is reachable.
• Common issues include missing environment variables or invalid bridge IDs; double-check the values in your config.json and Gentoro Studio.
• If you switch environments (dev/stage/prod), update GENTORO_BASE_URL accordingly and regenerate the GENTORO_KEY if used.