Kortex vs Prometheus MCP Server
A side-by-side look at the Kortex and Prometheus MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
K
KortexMonitoringWhich x402 service actually works: uptime, valid 402, and settlements proven on-chain.12EmergingAuth: not declaredVerdict: choose Kortex for monitoring work; choose Prometheus MCP Server for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Prometheus MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: other.
- You have the keys it needs:
PROMETHEUS_URL. - You want tools like
health_check, execute_query, execute_range_query.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | K Kortex | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 12/100 · Emerging | 60/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | PROMETHEUS_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 516 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 6 |
| Full listing | View Kortex | View Prometheus MCP Server |
Tools & capabilities
Kortex tools
No tool names declared yet. Check the project README from the listing page.
Prometheus MCP Server tools 6
health_checkHealth check endpoint for container monitoring and status verificationexecute_queryExecute a PromQL instant query against Prometheusexecute_range_queryExecute a PromQL range query with start time, end time, and step intervallist_metricsList all available metrics in Prometheus with pagination and filtering supportget_metric_metadataGet metadata for one metric or bulk metadata with optional filteringget_targetsGet scrape targets, with server-side `state`/`scrape_pool` filtering and optional pagination
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Kortex
No confirmed install command for Kortex yet — follow the setup steps linked from its listing page rather than a guessed package name.
Prometheus MCP Server
{
"mcpServers": {
"pab1it0-prometheus-mcp-server": {
"url": "https://hub.docker.com/mcp/server/prometheus/overview"
}
}
}
Frequently asked questions
Kortex is categorized under Monitoring and uses an install path we have not confirmed yet. Prometheus MCP Server belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Kortex for monitoring work and Prometheus MCP Server for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Kortex has no confirmed install command yet — follow its own setup instructions.
Kortex has no declared pricing — check the project's own site. Prometheus MCP Server is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kortex and pab1it0-prometheus-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kortex has a quality signal of 12/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Prometheus MCP Server has 60/100 (Good) with 4 views, 0 installs and 516 GitHub stars.