@genn-inc/cluebase-mcp

Cluebase MCP server. It speaks the Model Context Protocol over stdio, so your own AI tool can start a Cluebase analysis, follow it, and read the answer without leaving the tool you already use.

Node.js 20 or newer.

Add it to your AI tool

Most MCP-capable tools read a JSON file with an mcpServers object. Add one entry:

{
  "mcpServers": {
    "cluebase": {
      "command": "npx",
      "args": ["-y", "@genn-inc/cluebase-mcp"],
      "env": {
        "CLUEBASE_API_URL": "https://api.cluebase.example.com/api/v1",
        "CLUEBASE_MCP_TOKEN": "<token issued by Cluebase>",
        "CLUEBASE_MCP_ORGANIZATION_ID": "<your organization id>",
        "CLUEBASE_MCP_ACTOR_USER_ID": "<the Cluebase account this server acts as>"
      }
    }
  }
}

Restart the tool. The server is configured entirely by those four environment variables; there are no command-line flags and no configuration file.

The four variables

| Variable | What it is | | --- | --- | | CLUEBASE_API_URL | Base URL of the Cluebase API, including /api/v1. Defaults to http://localhost:4000/api/v1. | | CLUEBASE_MCP_TOKEN | The token Cluebase issued for this connection. Required; the server refuses to start without it. | | CLUEBASE_MCP_ORGANIZATION_ID | The organization the analyses belong to. Required. | | CLUEBASE_MCP_ACTOR_USER_ID | The Cluebase account this server acts as. An approval is a person's decision, so every analysis records who asked. Required. |

Check it works

printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"probe","version":"0"}}}' \
  | CLUEBASE_API_URL=... CLUEBASE_MCP_TOKEN=... CLUEBASE_MCP_ORGANIZATION_ID=... CLUEBASE_MCP_ACTOR_USER_ID=... \
    npx -y @genn-inc/cluebase-mcp

A single JSON line naming cluebase-mcp comes back. If nothing comes back, the four variables are not reaching the process — most tools require them inside the env object shown above rather than inherited from your shell.