Account

Manage Log10x credentials from inside the MCP, check which environments are reachable, and verify that the MCP install itself is wired up.

"sign me up for log10x"

Detected gh auth token — zero-click. Authenticated as GitHub talweiss → Log10x account talw@log10x.com. API key written to ~/.log10x/credentials. Default env: talweiss-default.

"which envs do I have?"

Signed in as talw@log10x.com. Envs: prod (OWNER, default), staging (WRITE), demo-shared (READ).

"health check"

All checks pass. Reporter detected, Retriever endpoint reachable, credentials valid.

You ask	Example answer
sign me up for log10x	One-click signup / signin via GitHub. Auto-opens the browser to authorize, exchanges the GitHub token for a Log10x API key, persists locally so every MCP host on the machine inherits it. Zero clicks if GitHub CLI is already authenticated.
log me out	Wipes local credentials at ~/.log10x/credentials and drops back to demo. Local-only — does not revoke the API key on log10x.com.
which Log10x environments do I have?	Identity plus every env reachable with permissions (OWNER / WRITE / READ), default env, last-used env. In demo mode, points at Sign in.
health check	Pass / warn / fail per check: environment vars, Prometheus reachability, Reporter detection, Retriever endpoint, credentials.

Prerequisites

Sign in needs a GitHub account. The other three need nothing.