Loki MCP Server

Created By
scottleppa year ago
An MCP ( Model Context Protocol ) Server for Grafana Loki
Overview

What is Loki MCP Server?

Loki MCP Server is a Go-based implementation of the Model Context Protocol (MCP) designed for integration with Grafana Loki, enabling efficient log data querying.

How to use Loki MCP Server?

To use the Loki MCP Server, build and run the server using Go or Docker. You can also test it with the provided client to execute log queries.

Key features of Loki MCP Server?

  • Implements the Model Context Protocol (MCP) for seamless communication.
  • Provides a Loki query tool for querying Grafana Loki log data.
  • Supports Docker for easy deployment and testing.
  • Modular architecture for easy extension and maintenance.

Use cases of Loki MCP Server?

  1. Querying logs from Grafana Loki for monitoring and debugging.
  2. Integrating with applications like Claude Desktop for enhanced log management.
  3. Testing and developing log query functionalities in a controlled environment.

FAQ from Loki MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol designed for communication between applications, allowing for efficient data exchange.

  • Is Loki MCP Server free to use?

Yes! The Loki MCP Server is open-source and free to use.

  • What are the prerequisites for running the server?

You need Go 1.16 or higher to build and run the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
scottlepp
Star
3
Language
Go
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago