orstrum serve

Start a stdio MCP server that exposes the graph as queryable tools.

$ orstrum serve [--cloud] [--config <path>]

The transport is always stdio — a standard MCP server launched as a subprocess by Claude Code, which speaks to it over stdin/stdout. There is no HTTP port.

Options

--cloud

flag

Serve the pushed Orstrum Cloud graph instead of the local .orstrum/graph.db. Requires orstrum login.

-c, --config <path>

string

Config file path. Defaults to the nearest orstrum.config.*.

Local vs. cloud mode

By default, orstrum serve reads the local .orstrum/graph.db and answers queries from it. Pass --cloud to serve the hosted graph you previously pushed with orstrum push — this requires a valid session in ~/.orstrum/credentials.json from orstrum login.

The same eight MCP tools are exposed in both modes with identical schemas. Cloud mode is chosen by the explicit --cloud flag — there is no config-driven auto-switch.

MCP client config

Register Orstrum with Claude Code by adding it to .claude/mcp.json in your project (or your global Claude Code MCP config):


  "mcpServers": 
    "orstrum": 
      "command": "orstrum",
      "args": ["serve"]

To serve the cloud graph instead, add "--cloud" to args, or register it directly: claude mcp add orstrum-cloud -- orstrum serve --cloud.