Tempo MCP Server

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

What is Tempo MCP Server?

Tempo MCP Server is a Go-based server implementation for the Model Context Protocol (MCP) that integrates with Grafana Tempo, allowing AI assistants to query and analyze distributed tracing data.

How to use Tempo MCP Server?

To use the Tempo MCP Server, you need to build and run it using Go or Docker. You can configure it to work with AI clients like Claude Desktop by adding it to the configuration file.

Key features of Tempo MCP Server?

  • Implements the Model Context Protocol (MCP) for AI integration.
  • Allows querying of Grafana Tempo trace data.
  • Supports Docker for easy deployment.

Use cases of Tempo MCP Server?

  1. Querying distributed tracing data for performance analysis.
  2. Integrating with AI assistants for automated data retrieval.
  3. Testing and developing tools that utilize tracing data.

FAQ from Tempo MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol that defines how AI clients can interact with tools and services.

  • Can I run the server without Docker?

Yes, you can build and run the server directly using Go.

  • What are the prerequisites for running the server?

You need Go 1.21 or higher and Docker for local testing.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
scottlepp
Star
0
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