Main
A good “observability loop” with langfuse-mcp:
- Ask your agent to reproduce a bug with tracing enabled.
- Use MCP tools to fetch the trace and identify the failing observation span.
- Pull the exact prompt version used (and labels), then patch the prompt and re-run.
If you want safer access in shared environments, enable read-only mode (--read-only) first.
README excerpt (verbatim)
Langfuse MCP Server
Model Context Protocol server for Langfuse observability. Query traces, debug errors, analyze sessions, manage prompts.
Why langfuse-mcp?
Comparison with official Langfuse MCP (as of Jan 2026):
| langfuse-mcp | Official | |
|---|---|---|
| Traces & Observations | Yes | No |
| Sessions & Users | Yes | No |
| Exception Tracking | Yes | No |
| Prompt Management | Yes | Yes |
| Dataset Management | Yes | No |
| Annotation Queues | Yes | No |
| Scores (v2) | Yes | No |
| Selective Tool Loading | Yes | No |
This project provides a full observability toolkit — traces, observations, sessions, exceptions, prompts, datasets, annotation queues, and scores — while the official MCP focuses on prompt management.
Tools (37 total)
| Category | Tools |
|---|---|
| Traces | fetch_traces, fetch_trace |
| Observations | fetch_observations, fetch_observation |
| Sessions | fetch_sessions, get_session_details, get_user_sessions |
FAQ
Q: How does it authenticate? A: README shows LANGFUSE_PUBLIC_KEY / LANGFUSE_SECRET_KEY and LANGFUSE_HOST via env vars.
Q: Can I restrict what loads?
A: Use --tools to load only the groups you need.
Q: Is there a safe mode?
A: README documents --read-only / LANGFUSE_MCP_READ_ONLY=true.