Summary

Admin questions answered in the client, with nothing writable behind them.

This is a read path onto software you are already running: dashboards, tenants, users, financials, logs, configuration and health, asked in plain language instead of clicked through in the admin UI. The credential it takes is the same root-tenant admin key the admin API uses, so decide once who holds it — after that the surface is reads only, and the data goes to your MCP client rather than to any third party.

What it is

The MCP server built into LastSaaS, an open-source multi-tenant SaaS foundation with a Go backend, a React frontend and MongoDB. It starts as a subcommand of the project's CLI, `lastsaas mcp`, runs over stdio, and proxies read-only requests to the LastSaaS admin API using an API key. Two resources, `lastsaas://dashboard` and `lastsaas://health`, are offered for automatic context.

What you get

A snapshot of users, tenants, health and active alerts, plus build and environment info — `dashboard_stats`, `get_about`
Tenant and user records with search and filters, and detail views carrying plan, billing, members, auth methods and memberships — `list_tenants`, `get_tenant`, `list_users`, `get_user`
Revenue, ARR, DAU and MAU time-series alongside searchable transaction history — `get_financial_metrics`, `list_transactions`
Full-text log search filtered by severity, category and date, and counts per severity level — `search_logs`, `get_log_severity_counts`
Current CPU, memory, disk and HTTP stats, time-series health per node or aggregate, the node list and third-party integration health — `get_system_health`, `get_health_metrics`, `list_nodes`, `get_integrations`
Runtime configuration variables, all of them or one at a time — `list_config`, `get_config`
Subscription plans with pricing and entitlements, the entitlement key catalog and credit bundle pricing — `list_plans`, `get_plan`, `list_entitlement_keys`, `list_credit_bundles`
Published and draft announcements, and Stripe promotion codes with their coupon details — `list_announcements`, `list_promotions`
An API key inventory that returns previews only, and the admin team with pending invitations — `list_api_keys`, `list_root_members`
Outbound webhook configurations, the event type reference and per-webhook delivery history — `list_webhooks`, `list_webhook_event_types`, `get_webhook`
No write operations — the server's tools read the admin API and nothing more

Requirements

A running LastSaaS instance, local or deployed, and a root-tenant API key with admin authority created in Admin → API Keys; keys carry the `lsk_` prefix. Both `LASTSAAS_URL` and `LASTSAAS_API_KEY` are required in the client's env block, and the client runs the binary with the `mcp` argument. Build that binary from `backend` with `go build -o lastsaas ./cmd/lastsaas`, or take the published `.mcpb` package (1.0.0) for darwin-arm64. Standing the application itself up needs Go 1.25+, Node.js 22+, MongoDB (Atlas or local) and Git; Resend, Stripe and OAuth credentials are listed as optional extras for email, billing and social sign-in. MIT licensed.