Account
Manage Log10x credentials from inside the MCP, check which environments are reachable, and verify that the MCP install itself is wired up.
You
sign me up for log10x
Log10x
Authenticated as GitHub talweiss → Log10x account talw@log10x.com. API key written to ~/.log10x/credentials. Default env: talweiss-default.
You
which envs do I have?
Log10x
Signed in as talw@log10x.com. Envs: prod (OWNER, default), staging (WRITE), demo-shared (READ).
You
health check
Log10x
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. |
| set me up against Grafana Cloud | Conversational onboarding — validates the backend, then writes ~/.log10x/envs.json. The metric tools point here whenever the env isn't configured. |
| create a staging env, make it default | Provisions a new env via the backend API. Friendly error if the name is already in use. |
make staging the default |
Rename or re-default an env. |
delete the old-poc env |
Destructive, confirm-name guarded. Refuses if the typed name doesn't match. |
| set my Datadog cost to $2.50/GB | Update account metadata: analyzer cost, AI provider, display name. |
| rotate my key | Confirm-string guarded. Replaces the API key, invalidates the old one server-side, writes the new one to ~/.log10x/credentials. |
Prerequisites
Sign in needs a GitHub account. Configure env and Health check work without an account. The env-management and key-management tools (create / update / delete / rotate / update settings) require signed-in credentials.