Replies: 10 comments 24 replies
-
|
Hi team, Thanks for asking for feedback! We've been using the new MCP tools with Cursor and really liking them so far. One workflow we use heavily is prompt stacking/dependencies for creating shared components (like system instructions or formatting templates) and referencing them in other prompts. The MCP integration handles creating these dependencies perfectly, which is great. The main thing missing for us right now: When we pull a prompt using It would be super helpful if Other than that, the validation and overall flow have been working really smoothly for us. Thanks for building this! |
Beta Was this translation helpful? Give feedback.
-
|
Hi guys, We're building an LLM-powered item prediction system and push failed predictions (no_match, validation failures, category mismatches) to Langfuse datasets for prompt improvement analysis. Being able to access and analyze this data through the MCP server would significantly improve our iteration workflow. Requested Tools
Why This MattersCurrently, analyzing failure patterns requires switching to the Langfuse web UI. Having MCP access would let us:
This would complement the existing prompt management tools nicely. We could analyze what's failing in datasets and immediately update prompts in the same workflow. |
Beta Was this translation helpful? Give feedback.
-
|
Im having issues getting claude code to work with the MCP server. I tried following these docs - https://langfuse.com/docs/api-and-data-platform/features/mcp-server but I'm consistently getting a 404 with the url - https://us.cloud.langfuse.com/api/public/mcp Connection failed: HTTP 404: Invalid OAuth error response: SyntaxError: JSON Parse error: The docs mention using But that domain doesnt seem to resolve at all? |
Beta Was this translation helpful? Give feedback.
-
|
@FroeMic that still isnt working. Here is what I see the the Claude mcp logs - https://gist.github.com/jchauncey/7c3c26e468c9a6f6e4547b9101f0b037 For the base64 token I'm following the instructions of - |
Beta Was this translation helpful? Give feedback.
-
|
if I have two projetcts called A and B, the mcp servers for A and B can't tell any meaningful difference |
Beta Was this translation helpful? Give feedback.
-
|
any plan to also add traces/ sessions in mcp ? |
Beta Was this translation helpful? Give feedback.
-
|
It would be useful to have a way to track prompt usage via the MCP server (e.g., seeing that prompt X was invoked 20 times) to help monitor usage. |
Beta Was this translation helpful? Give feedback.
-
|
Is self-hosted server support this feature? i access the url and it says 404 |
Beta Was this translation helpful? Give feedback.
-
|
Two feature requests: Tracing MCP (High priority): It seems like every other company is releasing an MCP to let Claude/Cursor agentically look at logs to understand what's happening and why. For example, Chrome's DevTools MCP is unbelievable for this–it can look at network logs, console, and navigate the screen to test full flows. Right now, there's no easy way for the Claude Code / Cursor to get Langfuse traces though. It'd be game changing if it can read through traces, understand where repeated errors happen, and then push prompt changes using the prompt MCP. You can hack pieces of this together, but it's quite inefficient today. This would get us to move all prompts to Langfuse vs other tools we're testing out. Return tagged prompt by default (Medium priority): In the Prompt Management MCP, there's a way to tell the AI to pull the unresolved "@@@langfusePrompt..." version, but in my testing even with custom instructions the AI (Opus 4.5 and 5.2 High) repeatedly struggle with this. So any plan review / feedback AI will call out a bug or DRY violation with prompts containing repeated information and not using the shared prompts we have. I think better MCP design would be to return what the user sees on default in Langfuse UI–the unresolved prompt. The AI is very good at understanding this and looking up its content, but when you start resolved by default it creates many more issues. |
Beta Was this translation helpful? Give feedback.
-
|
Does the current Langfuse prompt-management MCP support fetching prompts on a per-project basis? |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the feature or potential improvement
Help us improve the Langfuse MCP server
We recently launched a MCP Server built directly into Langfuse. It works with Claude Code, Cursor, and other MCP clients and currently provides tools for prompt management. We plan to add additional tools to cover our public api soon.
We want to take it further, and we'd love your input.
What we'd love to learn from you
Thanks for helping shape the future of AI-assisted workflows in Langfuse! 🙌
Additional information
If helpful, please include:
Beta Was this translation helpful? Give feedback.
All reactions