Langfuse
MCP server by Langfuse
Work with Langfuse prompts, observations, datasets, scores, evaluators and dashboards for LLM apps from your AI assistant.
Connect to Langfuse
Langfuse needs an API key. Connect with its own URL and your key:
Send your key. mcp.tc never sees or stores keys. Where to get a key
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/langfuseAbout
Connects an AI assistant to a Langfuse project, the open source LLM engineering platform for tracing, prompt management and evaluation. The assistant can work with prompts, observations, datasets, scores, evaluators and dashboards for your LLM applications.
Runs as a hosted streamable HTTP endpoint on Langfuse Cloud (https://cloud.langfuse.com/api/public/mcp), with US, Japan and HIPAA region endpoints, and at your-host/api/public/mcp for self-hosted instances. Authentication uses a Basic Authorization header built from your project public and secret API keys.
What you can do
- Read and manage prompts stored in Langfuse
- Inspect observations from LLM application traces
- Work with datasets used for evaluation
- Review and create scores
- Manage evaluators and dashboards
- Use cloud regions or a self-hosted Langfuse instance
Tools
Langfuse lists its tools only to clients with a key, so we can’t show them here.
Example prompts
List the prompts in my Langfuse project and show the latest version of each.
Show recent observations that had low scores in Langfuse.
Add these test cases to my Langfuse dataset for the support bot.
Which evaluators are configured in my Langfuse project?
Set up
Every client connects to cloud.langfuse.com. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http langfuse https://cloud.langfuse.com/api/public/mcp- Start Claude Code and type
/mcp. langfuse should show as connected.
Langfuse needs an API key. Langfuse’s docs say which header carries it; most servers use Authorization: Bearer <YOUR_API_KEY>.
Claude Desktop
- Use the
mcp-remotebridge, which keeps the key on this computer (a connector added on claude.ai with the key under Request headers also shows up here). Open Settings → Developer → Edit Config and add:
{
"mcpServers": {
"langfuse": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://cloud.langfuse.com/api/public/mcp"
]
}
}
}- Replace the placeholder with your key and restart Claude Desktop.
The bridge needs Node.js on your computer.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"langfuse": {
"url": "https://cloud.langfuse.com/api/public/mcp"
}
}
}Langfuse needs an API key. Langfuse’s docs say which header carries it; most servers use Authorization: Bearer <YOUR_API_KEY>.
VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"langfuse","type":"http","url":"https://cloud.langfuse.com/api/public/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"langfuse": {
"type": "http",
"url": "https://cloud.langfuse.com/api/public/mcp"
}
}
}Langfuse needs an API key. Langfuse’s docs say which header carries it; most servers use Authorization: Bearer <YOUR_API_KEY>.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"langfuse": {
"serverUrl": "https://cloud.langfuse.com/api/public/mcp"
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add langfuse --url https://cloud.langfuse.com/api/public/mcpOr edit ~/.codex/config.toml directly:
[mcp_servers.langfuse]
url = "https://cloud.langfuse.com/api/public/mcp"Langfuse needs an API key. Langfuse’s docs say which header carries it; most servers use Authorization: Bearer <YOUR_API_KEY>.
Gemini CLI
gemini mcp add --transport http langfuse https://cloud.langfuse.com/api/public/mcpThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"langfuse": {
"type": "http",
"url": "https://cloud.langfuse.com/api/public/mcp"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://cloud.langfuse.com/api/public/mcp.
Langfuse needs an API key. Langfuse’s docs say which header carries it; most servers use Authorization: Bearer <YOUR_API_KEY>.
Embed
Show Langfuse in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/langfuse)<a href="https://mcp.tc/i/langfuse"><img src="https://mcp.tc/i/langfuse/badge.svg" alt="Langfuse on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/langfuse.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/langfuse" title="Langfuse on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/langfuse.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Langfuse card to your site.
Add the mcp.tc card for Langfuse, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/langfuse.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="langfuse"><a href="https://mcp.tc/i/langfuse">Langfuse on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/langfuse)
```
Reference: https://mcp.tc/embedChange history
Its tools are behind a sign-in, so we can’t read them. Edits by its owner show up here.
Nothing recorded yet. Edits by the server’s owner will show up here.
FAQ
Can I paste mcp.tc/i/langfuse into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://cloud.langfuse.com/api/public/mcp, so your client talks to Langfuse directly. Your key goes there too, never to mcp.tc. The quick link is for sharing: it opens this page, with setup steps for every client.
Does Langfuse need an API key or a sign-in?
Yes. Langfuse needs an API key. Get one from Langfuse and keep it in your client’s config, never in a shared file.
Is Langfuse a remote or a local server?
Remote. Langfuse hosts it at https://cloud.langfuse.com/api/public/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can Langfuse do?
You can read and manage prompts stored in Langfuse, inspect observations from LLM application traces and work with datasets used for evaluation.
Which clients can use it?
Any client that supports remote MCP servers and can send your key: Claude Code, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. On claude.ai and Claude Desktop, add the key as a request header when you create the custom connector. ChatGPT can’t send a key, so it can’t use it.
Does mcp.tc track changes to Langfuse?
Partly. Langfuse’s tools are behind a sign-in, so its History tab shows only edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read Langfuse’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with Langfuse. This page was built from Langfuse’s public metadata, last checked on 17 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.