One command
Run one provider setup from an initialized project. Its adapter may handle auth inputs, run its available credential checks, then attempt persistence through Phantom. Supabase, Neon, Turso and Vercel have source resource-creation branches; other adapters attach accounts or supplied credentials. Inspect actual results.
stack add grafana
Or retrieve catalog matches for what you're building via stack recommend:
stack recommend "I need a observability provider"Auth flow
Supply the PAT required by the adapter. Available verification and storage phases vary; a check is not proof of every permission or resource.
How-to: Create a service-account token in Grafana → Administration → Service accounts, and provide your Grafana base URL.
Secret slots
stack add grafana has these 2 catalog secret
slots; verify which values its adapter actually materializes through Phantom:
GRAFANA_API_KEYGRAFANA_URL
Use stack env export --example for an empty-key skeleton.
Stack does not automatically fill env files or resolve credential placeholders.
stack exec -- <cmd> forwards to installed Phantom exec;
configure and verify the app separately.
Related providers in Observability
- Datadog — Metrics, traces, logs. Current adapter validates an API key via /api/v1/validate and stores that key only.
FAQ
Do I need a Grafana account to use it with Stack?
Use an existing Grafana account and permissions appropriate to the adapter. Creation or attachment behavior is provider-specific. Supply the PAT required by the adapter. Available verification and storage phases vary; a check is not proof of every permission or resource. If you don't have a credential yet, create one at https://grafana.com and supply the required inputs; inspect verification and persistence results.
Where does Stack store my Grafana credentials?
Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (GRAFANA_API_KEY, GRAFANA_URL); actual materialized outputs can differ. Stack handles supplied values in memory and records dedicated names in config; manual files and freeform metadata are not generally redacted.
Can I rotate or revoke this integration later?
Use `stack remove grafana` for local Grafana configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying Grafana credentials through https://grafana.com, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.