Skip to main content
Glama

Related Servers

Alternatives to langfuse-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      A
      maintenance
      MCP server for Langfuse observability. Query traces, debug exceptions, analyze sessions, and manage prompts and datasets for your LLM applications.
      48
      1,838 PyPI
      105
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Comprehensive MCP server for Langfuse, enabling AI assistants to access and manage traces, observations, scores, datasets, and sessions for observability.
      24
      8 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Dify Console API that enables managing apps, workflows, knowledge bases, models, plugins, and MCP servers programmatically from Claude Code or any MCP client.
      2 npm
      7
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Coolify API integration, enabling management of applications, databases, services, servers, and deployments via Claude Code or any MCP-compatible client.
      2 npm
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for orchestrating coding tasks with frontier-model planning and local execution, enabling manifest validation, plan submission, status checks, cancellation, and report retrieval through Claude Code.
      6
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes the Paperclip control plane API as tools for Claude Code agents — manage issues, coordinate agents, post comments, and orchestrate work without direct API calls.
      100
      33 npm
      2
      MIT

    TDQS

    B3.3/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., create_api_key vs. delete_api_key, list_traces vs. list_sessions). No overlap in purpose; descriptions are clear.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (create_*, delete_*, get_*, list_*, lookup_*, map_*) using snake_case with no mixing of conventions.

    Tool Count4/5

    20 tools is slightly above the typical 3-15 range but well-justified by the diverse resources (projects, keys, prompts, traces, etc.). No tool is redundant.

    Completeness2/5

    Several resource types lack CRUD coverage: no create/update for prompts, traces, observations, datasets, sessions; only list/get operations. API keys missing update. Major gaps for agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues