MCP Catalogs
Home

langfuse-mcp

by avivsinai·87·Score 48

Langfuse MCP server for AI agents to query trace data, debug exceptions, and manage observability.

ai-llmmonitoringdeveloper-tools
23
Forks
4
Open issues
this month
Last commit
2d ago
Indexed

Overview

The langfuse-mcp server provides comprehensive access to Langfuse observability data through the Model Context Protocol. It exposes 37 tools across multiple categories including traces, observations, sessions, exceptions, prompts, datasets, annotation queues, and scores. This allows AI agents to directly query production telemetry to answer critical questions about performance failures, user sessions, prompt versions, and dataset annotations. The server is actively maintained with recent commits and offers both read-only mode and selective tool loading for efficient token usage.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:Debugging failing agent runs by inspecting Langfuse traces and exception details
you:Analyzing slow generations and high-latency spans in production
you:Managing prompt versions, labels and datasets directly from AI workflows
you:How does this compare to the official Langfuse MCP server?
you:Can I limit the tools loaded to reduce token usage?

When to choose this

Choose this MCP server if you need comprehensive access to Langfuse observability data including traces, sessions, exceptions, and dataset management, especially when the official server's limited functionality isn't sufficient.

When NOT to choose this

Don't choose this if you only need prompt management capabilities (covered by the official server), or if you're concerned about potential vendor lock-in with Langfuse-specific features.

Tools this server exposes

12 tools extracted from the README
  • fetch_traces

    Fetch Langfuse trace data for debugging and analysis

  • fetch_trace

    Get details for a specific Langfuse trace

  • fetch_observations

    Retrieve observations from Langfuse traces

  • find_exceptions

    Find exceptions in Langfuse traces

  • get_session_details

    Get details for a specific Langfuse session

  • list_prompts

    List available prompts in Langfuse

  • get_prompt

    Retrieve a specific prompt from Langfuse

  • list_datasets

    List available datasets in Langfuse

  • create_dataset_item

    Create or update a dataset item in Langfuse

  • list_annotation_queues

    List annotation queues in Langfuse

  • list_scores_v2

    List scores in Langfuse v2

  • get_data_schema

    Get the data schema for Langfuse

Comparable tools

mcp-server-langfuselangfuse-apiopenobserve-mcpdatadog-mcp

Installation

Installation

**Using Claude Desktop (via project .mcp.json)**

{
  "mcpServers": {
    "langfuse": {
      "command": "uvx",
      "args": ["langfuse-mcp"],
      "env": {
        "LANGFUSE_PUBLIC_KEY": "pk-...",
        "LANGFUSE_SECRET_KEY": "sk-...",
        "LANGFUSE_HOST": "https://cloud.langfuse.com"
      }
    }
  }
}

**Using CLI**

# Claude Code
code mcp add \
  -e LANGFUSE_PUBLIC_KEY=pk-... \
  -e LANGFUSE_SECRET_KEY=sk-... \
  -e LANGFUSE_HOST=https://cloud.langfuse.com \
  langfuse -- uvx langfuse-mcp

# Codex CLI
codex mcp add langfuse \
  --env LANGFUSE_PUBLIC_KEY=pk-... \
  --env LANGFUSE_SECRET_KEY=sk-... \
  --env LANGFUSE_HOST=https://cloud.langfuse.com \
  -- uvx langfuse-mcp

FAQ

How does this compare to the official Langfuse MCP server?
This server provides a full observability toolkit including traces, observations, sessions, exceptions, prompts, datasets, annotation queues, and scores. The official MCP focuses only on prompt management, making this a more comprehensive solution for debugging and analyzing agent behavior.
Can I limit the tools loaded to reduce token usage?
Yes, use selective tool loading with `langfuse-mcp --tools traces,prompts` to load only specific tool groups. Available groups include traces, observations, sessions, exceptions, prompts, datasets, annotation_queues, scores, and schema.

Compare langfuse-mcp with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.