© 2026 Savi Finance — Internal proprietary system
Fetching identity data...
Services you watch most often. Status is refreshed from Railway when this tab loads.
Loading starred services...
Loading Railway services...

WHAT IS THIS?

Lobby ships an MCP server — a small endpoint your AI coding agent (Claude Code, Cursor, Gemini CLI, opencode, Antigravity, …) can connect to in order to do useful work against Savi's internal systems on your behalf.

Today it gives your agent read-only access to our internal MongoDB databases, read-only access to Railway (services, configs, logs), and a way to check your Savi identity. More tools will land here over time.

SERVER URL

Point your agent at this URL:

The first time you connect, your browser will open a Savi sign-in page. Approve once and your agent stays connected.

THINGS YOU CAN ASK YOUR AGENT — MONGODB

  • “Which Mongo instances does lobby know about?”
  • “List the collections in the sf1 database on the dev instance.”
  • “Describe the shape of the users collection — what fields are there and what types?”
  • “Show me the indexes on the transactions collection.”
  • “Find the 10 most recent transactions for user user_abc123.”
  • “How many sessions were created in the last 7 days?”
  • “Aggregate transactions by category and give me the top 5.”

Everything is read-only. The Mongo tools cannot insert, update, or delete — they will refuse any write-shaped query.

THINGS YOU CAN ASK YOUR AGENT — RAILWAY

  • “Which Railway projects does lobby have access to?”
  • “List the services in the savi-finance Railway project.”
  • “Show me the environments on that project.”
  • “What’s the current configuration of the lobby service in production — build command, replicas, healthcheck?”
  • “What variable names are set on the sf1/api service in production?”
  • “Pull the last 200 deploy log lines for the latest lobby deployment.”
  • “Show me the build logs from that failed deployment.”
  • “Who am I signed in as?”

Read-only and allowlisted. Lobby only talks to Railway projects explicitly allowlisted in its config — even though the underlying workspace token could reach more. Variable values are always redacted; only names are surfaced.

CONNECT — CLAUDE CODE

Run this once in your terminal:

Or add this to ~/.claude.json under mcpServers:

CONNECT — OPENCODE

Add this to ~/.config/opencode/opencode.json (or your project’s opencode.json):

CONNECT — CURSOR

Add this to ~/.cursor/mcp.json for all projects, or to .cursor/mcp.json at the root of a single project:

Then open Cursor Settings → MCP and toggle savi-lobby on.

CONNECT — GEMINI CLI

Add this to ~/.gemini/settings.json:

Note the key is httpUrl (Gemini CLI’s name for HTTP-transport servers), not url.

CONNECT — ANTIGRAVITY

In Antigravity, open Settings → Customizations → Open MCP Config and add:

Antigravity uses serverUrl (not url) for HTTP servers. Save the file and hit refresh in Installed MCP Servers.

Every action you take through Lobby — OAuth flows, MCP tool calls, admin operations — is recorded here. Anonymous events (failed sign-ins, unknown clients) appear under separate review and are not shown.
Loading audit log...
Periodic health checks run by the prober scheduler against production systems. Each cell is one run, oldest to newest — click a cell (or a row for the latest run) for the full result, including error details and metadata.
Loading prober grid...
Loading users...
Org-wide audit trail. Filter by user id or action prefix. Every access of this view is itself recorded as admin.audit_log_accessed.
Loading audit log...
Ready
env: production
not signed in