Hosting

Remote hosted or self-hosted

Transport

streamable-http

Endpoint

https://cloud.langfuse.com/api/public/mcp

Authentication

HTTP Basic authorization with project-scoped public and secret keys encoded as Base64.

Requirements

• Langfuse project and project-scoped API keys
• Choose endpoint for EU, US, Japan, HIPAA US, or self-hosted deployment

Setup steps

1. Create or copy the public and secret key in project settings.
2. Encode `publicKey:secretKey` as Base64 and configure `Authorization: Basic <BASE64_CREDENTIALS>` in the client secret facility.
3. Use the region-specific endpoint; US is https://us.cloud.langfuse.com/api/public/mcp, Japan https://jp.cloud.langfuse.com/api/public/mcp, HIPAA US https://hipaa.cloud.langfuse.com/api/public/mcp.
4. Reconnect and try a read-only operation such as listPrompts; apply client-side allowlists if restricting writes.

Two exact identifiers shown in the official Langfuse MCP setup examples. The canonical generated reference is the maintained complete roster; names and schemas can evolve.

• listPrompts

  List prompts from the connected Langfuse project.

  01
• listObservations

  List observations from the connected Langfuse project.

  02

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• Read and write tools are available by default; use client allowlists and approvals.
• Reverse proxy deployments may need the public Host header preserved or LANGFUSE_MCP_ALLOWED_HOSTS configured.

• official mcp reference

  Official reference lists both MCP servers, tools and evolving schemas.

• verified organization avatar

  Developer organization avatar; fallback tier D, visually checked.

• official documentation

  Current official publisher or maintainer documentation checked 2026-10-28T19:00:00.000Z.

Documentation checked 2026-10-28T19:00:00.000Z. Connection has not been runtime tested.