travsr serve
Start the SSE/HTTP MCP server, for cloud and team deployments where clients are not on the same machine as the index.
For a local editor or agent, use travsr mcp over stdio instead. serve exists for the remote case.
travsr serve --tenants-dir /srv/travsr/tenants
Options
| Flag | Default | Meaning |
|---|---|---|
--tenants-dir <DIR> | required | Directory containing per-tenant data subdirectories |
--host <HOST> | 127.0.0.1 | Bind address |
--port <PORT> | 3000 | Bind port |
It binds to loopback on purpose
The server speaks plaintext HTTP with bearer-token auth. It does not terminate TLS. Binding beyond this machine therefore has to be a deliberate act, not a default, so --host defaults to 127.0.0.1.
Pass --host 0.0.0.0 only when a TLS terminator sits in front of it. Exposing it directly puts bearer tokens on the wire in the clear.
Tenancy
Each subdirectory of --tenants-dir is one tenant's data. Requests are scoped to a tenant, and a tenant cannot read another's graph.
Tool surface
An SSE client can call 7 tools: get_dependencies, get_callers, get_blast_radius, get_lang_status, search_symbol, get_repo_map and get_execution_path. The rest of the 28 stdio tools, including every observability, synonym and repo-management tool, are stdio-only. The SSE server does not implement tools/list (it answers METHOD_NOT_FOUND), so a client has to know these names. See the MCP Tools Reference.