langfuse-mcp
Related Servers
Alternatives to langfuse-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceComprehensive MCP server for Langfuse, enabling AI assistants to access and manage traces, observations, scores, datasets, and sessions for observability.2410 npm1MIT
- AlicenseBqualityDmaintenanceModel Context Protocol server for Langfuse observability. Query traces, analyze accuracy, detect failures, track costs, debug latency, manage prompts and datasets.582MIT
- AlicenseNot gradedqualityDmaintenanceA read-only MCP server that enables agents to query and analyze Langfuse observability data, including traces, sessions, observations, scores, and metrics.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Langfuse providing 50 tools for prompt management, observability, instance/organization management, and metrics tracking via natural language.12 npmMIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for comprehensive monitoring and observability of systems using Langfuse.1MIT
- AlicenseBqualityDmaintenanceMCP server for Langfuse that lets Claude Code create projects, manage API keys, and query traces without touching the web UI. Designed to work with a self-hosted Langfuse v3 stack running locally via Docker Compose.20MIT
TDQS
Scored across 48 tools
Most tools map to a distinct resource+action, but the error/exception cluster (get_error_count, find_exceptions, find_exceptions_in_file, get_exception_details) and route-decision tools have overlapping analytical purposes. An agent can distinguish them only by carefully reading descriptions, and with 48 tools the misselection risk is elevated.
All tools use snake_case, but verb conventions are mixed across list/get/fetch/query/find/summarize/create/update/delete, and _v2 suffixes appear in list_scores_v2 and get_score_v2. The pattern is readable but not consistently predictable.
48 tools is well above the typical 3–15 range. Although Langfuse is a broad platform, the inclusion of many niche CRUD and route-decision tools makes the surface heavy and increases selection burden.
Core read/query workflows for traces, observations, sessions, metrics, prompts, and datasets are covered. However, management coverage has notable gaps: datasets lack update/delete, annotation queues lack update/delete, and scores have no create/delete surface.