Skip to content

Hosted Spor

Hosted Spor is the team version of the graph you run locally. Your organization gets one shared graph on the Spor server, running isolated from every other organization’s, and everyone on the team reads and writes the same nodes through the surfaces you already use: the spor CLI, the REST API, and the MCP connector. Nothing about the node format or the tools changes between local mode and hosted — what changes is that the graph is multiplayer, every write is attributed to the person or agent token that made it, and your data stays exportable in full (history included) at any time.

You will touch four hostnames:

Host What it is
app.sporhq.io The web app
api.sporhq.io The REST API — what the CLI and the web app talk to
mcp.sporhq.io The MCP connector, for claude.ai and other MCP hosts
auth.sporhq.io Sign-in and OAuth

A team-scoped token routes each request to your organization’s graph, so the same hostnames serve every organization without any of them seeing another’s data.

What the service can see and how you get your data out are stated in Data, privacy, and export; read it before you connect anything.

Joining is by invitation: an admin on your team invites you, you sign in at the hosted front door with your email, and your account becomes a member of the organization. From there:

  1. Sign in — see Organizations and sign-in.
  2. Connect your tools — point the CLI at api.sporhq.io and add the claude.ai connector; see Connecting your tools.
  3. Work normally. Queries, captures, the queue, and lenses behave exactly as in local mode, except your teammates’ writes show up too.

The first request after an idle period can take longer than later requests. If that keeps happening, see slow first request diagnostics for what to check.