A
licenseNot graded
qualityB
maintenanceA read-only MCP server that enables agents to query and analyze Langfuse observability data, including traces, sessions, observations, scores, and metrics.
MIT
langfuse-mcp
by hugoles
Related Servers
Alternatives to langfuse-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for Langfuse providing 50 tools for prompt management, observability, instance/organization management, and metrics tracking via natural language.10 npmMIT
- AlicenseAqualityBmaintenanceTypeScript MCP server that enables AI agents to manage LangSmith traces, prompts, datasets, experiments, and billing through natural language.151,569 npm17MIT
- AlicenseAqualityCmaintenanceComprehensive MCP server for Langfuse, enabling AI assistants to access and manage traces, observations, scores, datasets, and sessions for observability.2413 npm1MIT
- AlicenseCqualityAmaintenanceMCP server for Langfuse observability. Query traces, debug exceptions, analyze sessions, and manage prompts and datasets for your LLM applications.48105MIT
- AlicenseCqualityCmaintenanceAn MCP server implementation that integrates AI assistants with Langfuse workspaces, allowing models to query LLM metrics by time range.18 npm3Apache 2.0
TDQS
B3.1/5.0
Scored across 27 tools
Disambiguation5/5
Each tool targets a distinct resource or operation (e.g., getComment vs. listComments, getMetrics vs. getDailyMetrics). The 'get' vs 'list' prefix clearly differentiates single-item retrieval from multi-item listing. There is no meaningful overlap.
Naming Consistency5/5
All tools follow a consistent camelCase verb_noun pattern (e.g., getComment, listDatasets). The verbs are limited to 'get' and 'list', making the naming predictable and easy to understand.
Tool Count4/5
27 tools is on the higher side but still reasonable for a platform like Langfuse, which exposes many entity types (traces, observations, datasets, prompts, etc.). The count is not excessive and each tool serves a clear purpose.
Completeness2/5
The server is entirely read-only; there are no tools for creating, updating, or deleting resources. This is a significant gap for a full-featured MCP server, as agents cannot perform mutations that are likely needed in many workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues