Serving the cloud graph

After logging in and pushing a graph, point Claude Code at the hosted graph by running orstrum serve --cloud — the same stdio server, backed by Orstrum Cloud instead of your local .orstrum/graph.db.

How it works

orstrum serve --cloud starts the normal stdio MCP server but resolves every query against the graph you pushed to Orstrum Cloud, scoped to your workspace by the session in ~/.orstrum/credentials.json. There is no separate HTTP endpoint to configure — the transport is stdio, exactly as in local mode.

Registering with Claude Code

$ orstrum login
$ orstrum push
$ claude mcp add orstrum-cloud -- orstrum serve --cloud

Or add it to .claude/mcp.json directly:


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

Same tools, different backend

Cloud mode exposes the same eight tools with identical input schemas and output shapes as the local server. Switching between local and cloud is just the presence or absence of the --cloud flag — no tool calls need to change.

Roadmap: a direct HTTP endpoint (a URL you point an MCP client at with a bearer token, no local orstrum process) is planned but not yet available. Today, the hosted graph is served through the local orstrum serve --cloud process.