GenSX Cloud MCP server

@gensx/gensx-cloud-mcp is a Model Context Protocol server for GenSX Cloud workflows. It enables you to connect your GenSX Cloud workflows to MCP-compatible tools like Claude desktop, Cursor, and more.

Running a GenSX workflow from Claude desktop

Usage

Once you have run gensx deploy to deploy your project to the GenSX Cloud serverless runtime, you can consume those workflows via the @gensx/gensx-cloud-mcp server.

MCP-compatible tools use a standard JSON file to configure available MCP servers.

Update your MCP config file for your tool of choice to include the following:


{
  "mcpServers": {
    "gensx": {
      "command": "npx",
      "args": [
        "-y",
        "@gensx/gensx-cloud-mcp",
        "you_org_name",
        "your_project_name",
        "your_environment_name"
      ]
    }
  }
}

Your MCP client will run this command automatically at startup and handle acquiring the GenSX Cloud MCP server on your behalf. See the Claude desktop , and Cursor docs on configuring MCP servers for more details.

By default, the server reads your API credentials from the config saved by running the gensx login command. Alternatively, you can specify your GenSX API key as an environment variable in your MCP config:


{
  "mcpServers": {
    "gensx": {
      "command": "npx",
      "args": [
        "@gensx/gensx-cloud-mcp",
        "you_org_name",
        "your_project_name",
        "your_environment_name"
      ],
      "env": {
        "GENSX_API_KEY": "my_api_key"
      }
    }
  }
}

The GenSX build process automatically extracts input and output schemas from your typescript types, so no additional configuration or manual zod schema is required to consume your workflows from an MCP server.