F
licenseNot graded
qualityA
maintenanceEnables AI agents to query and debug Langfuse trace data, including traces, sessions, exceptions, route decisions, prompts, datasets, and metrics, for enhanced debugging and observability.
-
Langfuse Trace Fetcher
Related Servers
Alternatives to Langfuse Trace Fetcher
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to query and debug trace data from Langfuse, including sessions, exceptions, prompts, datasets, metrics, and annotation queues, through the Model Context Protocol.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to query Langfuse trace data for debugging and observability, with tools for traces, sessions, exceptions, routing decisions, prompts, datasets, scores, and metrics.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and developers to query Langfuse trace data for debugging and observability, including traces, sessions, exceptions, route decisions, prompts, datasets, and metrics. Supports local stdio/HTTP access through MCP clients with selective tool loading and read-only mode.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to query and debug Langfuse trace data, sessions, exceptions, prompts, datasets, scores, and metrics, with route-decision inspection and optional read-only or selective tool loading.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to locally debug Langfuse traces, sessions, and exceptions, and to query prompts, datasets, metrics, and annotation queues. It pairs with an included agent skill to provide trace debugging, exception triage, and latency analysis workflows.-
TDQS
A4.2/5.0
Scored across 3 tools
Disambiguation5/5
Each tool serves a distinct purpose: fetching a filtered list of traces, retrieving full detail for a specific trace, and listing available filter fields. There is no functional overlap.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern (fetch_langfuse_traces, get_langfuse_trace_detail, list_langfuse_trace_filters) with snake_case, making the naming predictable and clear.
Tool Count5/5
With 3 tools, the set is well-scoped for a trace fetching server: listing with filters, getting detail, and a reference tool for filters. No extraneous or missing tools.
Completeness5/5
For a 'Trace Fetcher', the tools cover the core workflow: querying traces with filters, retrieving individual details, and discovering available filters. No essential operations are missing.
Maintenance
ActivityInactive
ResponsivenessNo recent community issues