app_status

com.gemmein/mcp · Verify this server

Returns the app this connection is approved for: its name, its Development public key (pk_ — public by design, the key the app's code uses; no secret key is ever returned here), whether it is live, and what going live still waits on, each in plain words. Then its status across the board, per environment: Stripe connected or not, each AI provider key's last call (never the key), each AI tool ready, waiting or switched off, each relay's dead, failing and queued runs, Development's caps used of their limit and when they open again, the app's domains and email (web, sending, receiving), approvals waiting in the founder's browser, and what Live still needs — each line ok, or a problem with its fix and whose step that is (the founder's, or the AI's). Useful for how the app stands, and before going live comes up. Needs the founder's Gemmein account: on the first call the AI app opens their browser to approve this connection in the Gemmein dashboard — one approval lets this connection build the app in Development (revocable on Approvals). Live is never part of it: each Live change is approved on its own in the browser — a change to one customer is the founder's approval alone; going live is the founder's approval, then paying for the plan, with no code; a change to how the business runs (a promote or a Live push, products and prices, domains, email, Stripe, keys, relays and AI tools, the Live site) also asks for the code Gemmein emails and, when set up, their authenticator app's code (request_live_action). This is what a founder may call how the app stands, or what is left to do.