query-layer
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@query-layerping the query layer to check if it's responsive"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Server for Query Layer API
An MCP (Model Context Protocol) server that exposes a metrics query-layer API to AI assistants. Built with the official Python MCP SDK v2.
Quick Start
# Prerequisites: Python 3.10+, uv
uv sync
uv run mcp dev src/server.pyOpen the MCP Inspector at the URL printed to the console. You'll see the ping tool available.
Related MCP server: prometheus-mcp
Cursor Integration
The .cursor/mcp.json file is pre-configured. Restart Cursor and the query-layer MCP server will be available to the AI assistant.
Local Tracing with Phoenix (Optional)
# Terminal 1: start Phoenix
uv run phoenix serve
# Terminal 2: run the server pointing at Phoenix
export PHOENIX_COLLECTOR_ENDPOINT=http://localhost:6006
uv run mcp dev src/server.pyView traces at http://localhost:6006 — Phoenix natively renders MCP tool calls, prompts, and GenAI spans.
Documentation
Document | Purpose |
Problem statement, solution approach, implementation plan | |
Production-grade plan review | |
MCP concepts, technology choices, design decisions | |
Setup, install, run, configure, troubleshoot | |
Logging, tracing, OTLP, local Phoenix |
Project Structure
src/
server.py # MCPServer + tools (entry point)
logging_config.py # Structured JSON logging to stderr
otel_config.py # OpenTelemetry exporter configuration
.cursor/
mcp.json # Cursor MCP server configuration
docs/
plan.md # Full implementation plan
review.md # Plan review
design.md # Design document
getting-started.md # Setup guide
observability.md # Observability guideLicense
Apache 2.0 — see LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Exposes FEDLIN's public security scanners as agent-callable tools over Streamable HTTP.
Gateway between LLM agents and world data through eight tools and a bundled endpoint catalog.
Query application logs, traces, and metrics from your AI coding assistant via Foam's MCP server.
Analytics for MCP servers. Query your tool calls, first-call success, retries and schema cost.
Related MCP Servers
- AlicenseAqualityAmaintenanceProvides access to Prometheus metrics and queries through standardized Model Context Protocol interfaces, allowing AI assistants to execute PromQL queries and analyze metrics data.6514MIT
- AlicenseBqualityDmaintenanceProvides seamless integration between AI assistants and Prometheus, enabling natural language interactions with your monitoring infrastructure. This server allows for effortless querying, discovery, and analysis of metrics.103,324 npm27MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query Prometheus metrics, monitor alerts, and analyze system health through read-only access to your Prometheus server with built-in query safety and optional AI-powered metric analysis.MIT
- FlicenseBqualityDmaintenanceEnables AI assistants to interact with Datadog APIs for querying metrics, logs, events, monitors, and APM traces.164-