Langfuse Docs MCP Server for Claude

Overview

Langfuse publishes a public Docs MCP server at https://langfuse.com/api/mcp. It exposes Langfuse documentation search and page retrieval to MCP clients, so Claude Code, Cursor, Copilot, Windsurf, and other agents can find current Langfuse implementation guidance without scraping the website by hand.

Use this listing for the unauthenticated docs endpoint. Langfuse also documents an authenticated platform MCP server for project data at /api/public/mcp; that server is useful for prompts, traces, datasets, metrics, comments, evaluators, and scores, but it carries real project authority and should be configured more carefully.

Server Types

Install In Claude Code

Add the public docs server:

claude mcp add \
  --transport http \
  langfuse-docs \
  https://langfuse.com/api/mcp \
  --scope user

Then start Claude Code and run /mcp to confirm the langfuse-docs server is connected.

Manual Configuration

Add this to a Claude settings file:

{
  "mcpServers": {
    "langfuse-docs": {
      "transportType": "http",
      "url": "https://langfuse.com/api/mcp",
      "verifySsl": true
    }
  }
}

For clients that expect stdio rather than Streamable HTTP, Langfuse documents mcp-remote as a local proxy pattern:

{
  "mcpServers": {
    "langfuse-docs": {
      "command": "npx",
      "args": ["mcp-remote", "https://langfuse.com/api/mcp"]
    }
  }
}

Docs Tools

The MCP reference currently identifies three public docs tools:

The same docs search is also exposed as a REST endpoint at https://langfuse.com/api/search-docs for lightweight non-MCP workflows.

Authenticated Platform MCP

When an agent needs project data instead of docs, configure the authenticated Langfuse MCP server with a project-scoped public key and secret key encoded in a Basic Auth header:

claude mcp add --transport http langfuse https://cloud.langfuse.com/api/public/mcp \
  --header "Authorization: Basic <base64(LANGFUSE_PUBLIC_KEY:LANGFUSE_SECRET_KEY)>"

Langfuse documents regional cloud endpoints for US, Japan, and HIPAA US regions, plus a self-hosted endpoint at https://your-domain.com/api/public/mcp.

The platform MCP is broader than the docs endpoint. The MCP reference lists tools for prompt lookup and creation, prompt-label updates, observations, annotation queues, comments, datasets, dataset items, dataset runs, scores, score configs, metrics, models, media, evaluators, evaluation rules, and health checks. Both read and write tools are available by default, so configure your client's tool allowlist if the agent should only inspect data.

Use Cases

• Ask Claude Code to find the current Langfuse tracing setup for a framework.
• Let Cursor retrieve the right docs page before instrumenting an existing OpenAI, LangChain, LangGraph, or agent workflow.
• Compare prompt-management, evaluation, and observability docs without leaving the editor.
• Use the authenticated platform MCP to list prompts, inspect observations, pull dataset items, or create evaluation artifacts after project credentials are scoped and reviewed.
• Pair the Docs MCP with the Langfuse Agent Skill when an agent can benefit from both source-aware documentation search and a repeatable implementation playbook.

Safety and Privacy

Keep the two server surfaces separate. The public Docs MCP is useful context for implementation and troubleshooting, but it does not prove anything about your own Langfuse project. The authenticated platform MCP can access real project data and may create or update resources such as prompts, scores, comments, datasets, evaluators, or evaluation rules.

For production projects, prefer project-scoped keys, store the Basic Auth header in local MCP configuration instead of prompts, and restrict write tools when the agent only needs investigation access. Review generated code before enabling tracing in production because traces can capture prompts, model outputs, tool arguments, costs, latency, metadata, and customer-sensitive payloads.

Source Review

Verified on 2026-06-18:

• Langfuse's Docs MCP page documents https://langfuse.com/api/mcp, Streamable HTTP transport, no authentication, Claude Code setup, Cursor, Copilot, Windsurf, mcp-remote, MCP reference links, and the REST search-docs endpoint.
• Langfuse's API and data-platform MCP page documents the authenticated /api/public/mcp endpoint, regional cloud endpoints, self-hosted endpoint, Basic Auth setup, and the warning that read and write tools are available by default unless the client restricts them.
• The Langfuse MCP reference documents a public Docs MCP server and an authenticated Cloud MCP server, including docs tools and platform tool categories.
• The existing HeyClaude Langfuse entry is a general tools listing for the observability platform. This entry is limited to the MCP connection surfaces, with the public docs endpoint as its canonical source.

Duplicate Check

Checked current content/mcp/, content/tools/, content/skills/, open pull requests, and prior closed PR history for Langfuse MCP, langfuse-docs, https://langfuse.com/api/mcp, https://cloud.langfuse.com/api/public/mcp, and mcp.reference.langfuse.com. The catalog already has content/tools/langfuse.mdx for the general Langfuse platform. A prior closed MCP attempt used the generic Langfuse repository as its canonical source and was rejected as same-source ambiguous. This resubmission is narrowed to the official Docs MCP and MCP reference sources, with explicit separation from the general tools listing.