A Go-based server implementation for the Model Context Protocol (MCP) with Grafana Loki integration.
Connect Gigapipe Logs MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Go-based server implementation for the Model Context Protocol (MCP) with Grafana Loki integration. The gigapipe logs mcp mcp server is what makes that connection.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
query — LogQL query stringurl — The Loki server URL (default: from LOKI_URL environment variable or http://localhost:3100)start — Start time for the query (default: 1h ago)end — End time for the query (default: now)limit — Maximum number of entries to return (default: 100)org — Organization ID for the query (sent as X-Scope-OrgID header)LOKI_URL — Default Loki server URL to use if not specified in the requestLOKI_ORG_ID — Default organization ID to use if not specified in the requestLOKI_USERNAME — Default username for basic authentication if not specified in the requestLOKI_PASSWORD — Default password for basic authentication if not specified in the requestLOKI_TOKEN — Default bearer token for authentication if not specified in the requestAuthentication — Choose appropriate authentication if neededSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Configuration is passed through the environment: LOKI_URL, LOKI_ORG_ID, LOKI_USERNAME, LOKI_PASSWORD, LOKI_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Gigapipe Logs MCP's toolset — query, url, start and 11 more — is a fair guide to whether it matches your workflow. It is maintained by gigapipehq; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Gigapipe Logs MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| query | LogQL query string |
| url | The Loki server URL (default: from LOKI_URL environment variable or http://localhost:3100) |
| start | Start time for the query (default: 1h ago) |
| end | End time for the query (default: now) |
| limit | Maximum number of entries to return (default: 100) |
| org | Organization ID for the query (sent as X-Scope-OrgID header) |
| LOKI_URL | Default Loki server URL to use if not specified in the request |
| LOKI_ORG_ID | Default organization ID to use if not specified in the request |
| LOKI_USERNAME | Default username for basic authentication if not specified in the request |
| LOKI_PASSWORD | Default password for basic authentication if not specified in the request |
| LOKI_TOKEN | Default bearer token for authentication if not specified in the request |
| Authentication | Choose appropriate authentication if needed |
| Server | The main MCP server implementation in cmd/server/main.go |
| Client | A test client in cmd/client/main.go for interacting with the MCP server |
{
"mcpServers": {
"lokiserver": {
"command": "path/to/loki-mcp-server",
"args": [],
"env": {
"LOKI_URL": "http://localhost:3100",
"LOKI_ORG_ID": "your-default-org-id",
"LOKI_USERNAME": "your-username",
"LOKI_PASSWORD": "your-password",
"LOKI_TOKEN": "your-bearer-token"
},
"disabled": false,
"autoApprove": ["loki_query"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LOKI_URL | Endpoint or connection string the server talks to. | Yes |
| LOKI_ORG_ID | Configuration value read at startup. | Optional |
| LOKI_USERNAME | Configuration value read at startup. | Optional |
| LOKI_PASSWORD | Configuration value read at startup. | Optional |
| LOKI_TOKEN | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.