Bring Llm Tracing
to Claude Desktop
Learn how to connect Langfuse (LLM Tracing & Evals) to Claude Desktop and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
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 a new LLM observation (span, event, generation) inside a trace
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
Generate rolled-up USD cost and aggregated latency statistics
Retrieve explicit span or generation context within a trace
Get complete telemetry and nested graph for a single trace
List raw observation objects spanning across traces
Extract actively managed prompt templates and versions
List all explicit scores mapping quality or cost algorithms
List high-level user session entities encapsulating multiple traces
List all traces tracking LLM API sessions
Why Claude Desktop?
Claude Desktop is the definitive way to connect Langfuse (LLM Tracing & Evals) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Langfuse (LLM Tracing & Evals) in Claude Desktop
Langfuse (LLM Tracing & Evals) and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Langfuse (LLM Tracing & Evals) to Claude Desktop 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Langfuse (LLM Tracing & Evals) in Claude Desktop
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 Desktop 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.
* 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
How Vinkius secures
Langfuse (LLM Tracing & Evals) for Claude Desktop
Every tool call from Claude Desktop 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.
Frequently asked questions
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.
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.
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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.