← Explore all mcp servers

OBSERVABILITY / Langfuse

Langfuse data MCP

Inspect Langfuse observations, prompts and evaluation data, and manage supported project resources through its native MCP endpoint.

“Both read and write tools are available by default.”

01 / THE REASONING

Why this made the selection.

  • Brings prompts, observations, scores and evaluation datasets into an agent’s investigation.
  • Project-scoped API credentials and regional endpoints make the data boundary explicit.
  • Langfuse documents a stateless project-scoped MCP server that uses an API key, with both read and write tools available unless the client allowlists read-only tools.
  • The reference site separates that authenticated project server from an unauthenticated documentation server and tells clients not to assume a fixed tool list.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • Native Langfuse MCP setup guide and generated MCP Reference.
  • https://langfuse.com/docs/api-and-data-platform/features/mcp-server
  • https://mcp.reference.langfuse.com
  • Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

Our findings

  • The server uses stateless Streamable HTTP with project API-key Basic authentication.
  • The current reference includes prompt, dataset, score and annotation mutations; it is broader than prompt retrieval.
  • The Langfuse data MCP server is stateless, and each API key is scoped to one project. The reference calls that endpoint an authenticated project-scoped server.
  • Read and write tools are available by default. Restricting writes is described as a client allowlist, not as a separate server mode on this page.
  • A second, unauthenticated server is documented for documentation search. Clients are told to inspect tools dynamically. The page says Pi does not include built-in MCP support.
  • The current project MCP exposes reads and writes by default; observation tools distinguish logical roots from physical parent relationships.

Not established by this review

  • Server launch, authenticated tool calls, and release-to-source parity were not tested.
  • The resource was not executed and its tools were not called.
  • The server was not called. A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. Choose the documented cloud-region endpoint, or your self-hosted /api/public/mcp endpoint.
  2. Create project API keys and configure Basic authentication using the official client instructions; keep secrets outside shared project files.
  3. Apply a read-only tool allowlist if the agent should investigate without changing project data.

Before you start

  • Langfuse project API keys.
  • A client supporting Streamable HTTP and the required authorization header.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "langfuse-cloud": {
      "url": "https://cloud.langfuse.com/api/public/mcp",
      "headers": {
        "Authorization": "Basic <base64(LANGFUSE_PUBLIC_KEY:LANGFUSE_SECRET_KEY)>"
      }
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://langfuse.com/docs/api-and-data-platform/features/mcp-server

    Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review

  2. https://mcp.reference.langfuse.com

    Supports: summary, whySelected, bestFor, access, limitations, review

Evidence & Ask