Skip to main content
Glama
KarandeepSinghSodhi

Langfuse Trace Fetcher

by KarandeepSinghSodhi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Langfuse Trace Fetcher

No user-submitted related servers found.

    Related Servers

    • LLMemory

      meir-may
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables VS Code agent mode to search and retrieve context from your LLMemory vault of AI conversations (ChatGPT, Claude, etc.) without copying and pasting.
      6 npm
      MIT

    • langfuse-mcp-java

      Log-LogN
      A
      license
      B
      quality
      D
      maintenance
      Query Langfuse traces, schema and datasets, scores and metrics, debug exceptions, analyze sessions, and manage prompts. Full observability toolkit for LLM applications.
      55
      3
      MIT

    • Shepherd MCP

      neuralis-in
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to query and analyze AI agent sessions from observability providers like Shepherd (AIOBS) and Langfuse, allowing users to debug agent runs, compare sessions, track performance, and analyze LLM usage patterns.
      18
      MIT

    • Langfuse MCP Server

      therealsachin
      A
      license
      B
      quality
      D
      maintenance
      Enables querying Langfuse analytics, cost metrics, and usage data across multiple projects. Provides tools for trace analysis, model/service cost breakdowns, and daily usage trends through natural language queries.
      24
      49 npm
      MIT

    • memgrep

      gitwork-oss
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to search and retrieve past chat transcripts from Cursor, Claude Code, and Kiro, providing a global, local memory for context-aware assistance.
      675 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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 issues

    Resources