Can I use Prometheus as a CLI?

Yes. KosmoKrator exposes a Prometheus CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Prometheus through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Prometheus tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Prometheus credentials stored?

Prometheus credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Prometheus MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

analytics

Prometheus CLI for Headless Automation

Use the Prometheus CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 7 read 0 write API token auth

Submit Prometheus feedback View package source

Prometheus CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Prometheus CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Prometheus CLI for Headless Automation
kosmokrator integrations:configure prometheus --set api_token="$PROMETHEUS_API_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call prometheus.prometheus_list_alerts '{"filter":"example_filter","receiver":"example_receiver"}' --json

Discovery Before Execution

Agents and scripts can inspect Prometheus docs and schemas before choosing a function.

kosmo integrations:docs prometheus --json
kosmo integrations:docs prometheus.prometheus_list_alerts --json
kosmo integrations:schema prometheus.prometheus_list_alerts --json
kosmo integrations:search "Prometheus" --json
kosmo integrations:list --json

Useful Prometheus CLI Functions

Function	Type	Parameters	Description
`prometheus.prometheus_list_alerts`	Read	filter, receiver	List Prometheus alerts. Optionally filter by alert state or label selectors. Returns alert names, states, labels, and annotations.
`prometheus.prometheus_get_alert`	Read	name	Get a Prometheus alert by name. Returns the full alert definition including labels, annotations, and state.
`prometheus.prometheus_list_rules`	Read	type	List Prometheus alerting and recording rules. Optionally filter by type. Returns rule groups with their rules and states.
`prometheus.prometheus_get_rule`	Read	name	Get a Prometheus rule group by name. Returns the full rule group definition including all rules within the group.
`prometheus.prometheus_list_targets`	Read	state	List Prometheus scrape targets. Optionally filter by state (active or dropped). Returns target health status, labels, and scrape info.
`prometheus.prometheus_get_target`	Read	instance	Get a Prometheus target by its instance address. Returns target health, last scrape info, and discovery labels.
`prometheus.prometheus_get_current_user`	Read	none	Get the current authenticated Prometheus user info. Useful for verifying authentication and retrieving user details.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Prometheus CLI Pages

CI Prometheus CLI for CI. Cron Jobs Prometheus CLI for cron jobs. Shell Scripts Prometheus CLI for shell scripts. Coding Agents Prometheus CLI for coding agents.