3,400+ servers built on vurb.ts
Vinkius

Bring Llm Tracing
to Claude Code

Learn how to connect Langfuse (LLM Tracing & Evals) to Claude Code and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Create ObservationCreate ScoreGet Daily MetricsGet ObservationGet TraceList ObservationsList PromptsList ScoresList SessionsList Traces
Langfuse (LLM Tracing & Evals)

What is the Langfuse (LLM Tracing & Evals) MCP Server?

Connect your Langfuse account to any AI agent and take full control of your LLM observability, prompt management, and quality evaluation through natural conversation.

What you can do

  • Trace Orchestration — List and retrieve detailed traces of LLM API sessions, exposing latencies, token counts, and exact chained payloads directly from your agent
  • Prompt Vault Access — Query actively managed prompt templates and versions to inspect system instructions and expected input variables
  • Observation Analysis — Deep-dive into individual spans, events, and generations within a trace to pinpoint failures or performance bottlenecks securely
  • Evaluation & Scoring — Attach structured human feedback or automated evaluation metrics to specific traces to monitor model grounding and accuracy
  • Usage Metrics — Generate aggregated daily reports on USD costs and average latency to track your AI infrastructure spending in real-time
  • Session Monitoring — Extract correlated user sessions to understand multi-turn interaction boundaries and improve long-term agentic workflows

How it works

1. Subscribe to this server
2. Enter your Langfuse API URL, Public Key, and Secret Key
3. Start monitoring your LLM application from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • LLM Engineers — debug complex AI chains and measure exact token latencies through natural conversation without manual dashboard searching
  • Product Owners — monitor daily AI costs and user satisfaction scores across multiple production environments
  • Data Scientists — manage prompt templates and audit evaluation metrics to improve model response quality and grounding efficiently

Built-in capabilities (10)

create_observation

Create a new LLM observation (span, event, generation) inside a trace

create_score

g. 1-5 stars) or automated pipeline metrics bounding exactly onto the specified Trace or Observation. Attach human feedback or evaluation metrics to a trace/observation

get_daily_metrics

Generate rolled-up USD cost and aggregated latency statistics

get_observation

Retrieve explicit span or generation context within a trace

get_trace

Get complete telemetry and nested graph for a single trace

list_observations

List raw observation objects spanning across traces

list_prompts

Extract actively managed prompt templates and versions

list_scores

List all explicit scores mapping quality or cost algorithms

list_sessions

List high-level user session entities encapsulating multiple traces

list_traces

List all traces tracking LLM API sessions

Why Claude Code?

Claude Code registers Langfuse (LLM Tracing & Evals) as an MCP server in a single terminal command. Once connected, Claude Code discovers all 10 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where Langfuse (LLM Tracing & Evals) data drives decisions without human intervention.

  • Single-command setup: claude mcp add registers the server instantly. no config files to edit or applications to restart

  • Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks

  • Claude Code runs headlessly, enabling unattended batch processing using Langfuse (LLM Tracing & Evals) tools in cron jobs or deployment scripts

  • Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features

See it in action

Langfuse (LLM Tracing & Evals) in Claude Code

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Langfuse (LLM Tracing & Evals) and 3,400+ other MCP servers. One platform. One governance layer.

Teams that connect Langfuse (LLM Tracing & Evals) to Claude Code through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

3,400+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself3,400+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Langfuse (LLM Tracing & Evals) in Claude Code

The Langfuse (LLM Tracing & Evals) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Claude Code only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Langfuse (LLM Tracing & Evals)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Langfuse (LLM Tracing & Evals) for Claude Code

Every tool call from Claude Code to the Langfuse (LLM Tracing & Evals) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I see the exact system instruction for a specific prompt version?

Yes. Use the list_prompts tool to browse your managed templates. Your agent can retrieve the exact text and variables for any deployed prompt version, making it easy to audit AI logic through natural conversation.

02

How do I log human feedback for a specific trace?

Use the create_score tool by providing the Trace ID and a JSON payload defining the score name (e.g. 'user-satisfaction') and value. Your agent will attach this structured data directly to the Langfuse record.

03

Can my agent report on my LLM spending for the current day?

Absolutely. The get_daily_metrics tool retrieves aggregated USD costs and average latency metrics from Langfuse. Your agent can summarize these statistics to help you monitor your infrastructure budget in real-time.

04

How do I add an MCP server to Claude Code?

Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.

05

Can Claude Code run MCP tools in headless mode?

Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.

06

How do I list all connected MCP servers?

Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.

07

Command not found: claude

Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code

08

Connection timeout

Check your internet connection and verify the Edge URL is reachable