Lastsaas
Let your coding agent query LastSaaS admin data—users, tenants, billing, logs, and health—without opening the dashboard.
Overview
io.github.jonradoff/lastsaas is an Operate-phase MCP server that gives read-only LastSaaS admin access—dashboards, users, tenants, billing, logs, and health—to AI coding agents.
What is this MCP server?
- Read-only admin MCP—safe for agents without mutating production data
- Covers dashboards, users, tenants, billing, logs, and health in one stdio server
- Connects via LASTSAAS_URL plus root-tenant API key (lsk_) from Admin → API Keys
- Ships as mcpb binary (e.g. darwin-arm64) over stdio transport
- Targets LastSaaS instances on Fly, localhost:4290, or your deployed base URL
- Server version 1.0.0 with stdio transport via mcpb registry package
- Two required environment variables: LASTSAAS_URL and LASTSAAS_API_KEY
- Documented admin surfaces: dashboards, users, tenants, billing, logs, health (read-only)
Community signal: 111 GitHub stars.
What problem does it solve?
You are running a LastSaaS app and waste time context-switching between the admin UI and your agent when you need tenant, billing, or log facts mid-debug.
Who is it for?
Solo builders already on LastSaaS who want agent-assisted ops reviews, support triage, and health checks with read-only guardrails.
Skip if: Teams not on LastSaaS, or anyone who needs write/admin mutations, infra provisioning, or generic CRM integrations outside LastSaaS.
What do I get? / Deliverables
After you register the server with your instance URL and admin API key, your agent can pull structured LastSaaS operational data in chat while you stay in the repo or terminal.
- Agent-queryable read-only views of LastSaaS dashboards, users, tenants, billing, logs, and health
- Faster operational answers without leaving the IDE during incident or support work
Recommended MCP Servers
Journey fit
Operate is where you keep a live SaaS healthy; this server is built for day-two admin visibility, not greenfield coding. Monitoring fits dashboards, logs, and health checks; billing and tenant views support operational triage alongside uptime.
How it compares
LastSaaS-specific read-only admin MCP—not a generic Postgres or Stripe skill and not a deploy CLI.
Common Questions / FAQ
Who is io.github.jonradoff/lastsaas for?
It is for LastSaaS operators—especially solo founders—who want Claude Code, Cursor, or similar agents to read admin metrics and records without manual dashboard hopping.
When should I use io.github.jonradoff/lastsaas?
Use it during Operate when you are investigating tenant issues, billing anomalies, log patterns, or health regressions on a running LastSaaS instance.
How do I add io.github.jonradoff/lastsaas to my agent?
Install the mcpb release for your platform, add the MCP server in your agent config with stdio transport, and set LASTSAAS_URL and LASTSAAS_API_KEY (root-tenant lsk_ key from Admin → API Keys).