Skip to content
Vinkius

Langfuse Trace URL Extractor Connector for AI agents.

3 live capabilities

Turn raw Langfuse logs into clickable dashboard links.

Live agent request Langfuse Trace URL Extractor / Connector

Waiting for input…

AI Agent

Why people use Langfuse Trace URL Extractor

Stop hunting through JSON logs with Langfuse Trace URL Extractor

With this MCP, you just point your agent at the log. It finds the IDs and gives you the link. You click once and you are in the dashboard.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You stop hunting for links and start debugging traces.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 6,100+ Connectors

  1. Real-world use case 01

    Found a broken trace in your logs?

    Ask your agent to extract the ID and give you the link so you can see the error immediately.

  2. Real-world use case 02

    Checking if a new log format is compatible?

    Use the validation capability to verify the schema against Langfuse requirements instantly.

  3. Real-world use case 03

    Automating error reports in CI/CD

    Have your agent generate direct Langfuse links for every error found during automated testing.

Complete set · 3capabilities

The complete Langfuse Trace URL Extractor capability set.

These are the exact actions your AI can choose when you ask it to work with Langfuse Trace URL Extractor.

Capability set01 / 01

01—03

3 capabilities in this set.

Part of 3 available through Langfuse Trace URL Extractor.

  1. 01 Capability

    Extract trace identifiers

    Pulls trace and project IDs out of raw JSON payloads so you do not have to hunt for them.

  2. 02 Capability

    Validate payload schema

    Checks if your JSON data actually contains the required fields before you try to process it.

  3. 03 Capability

    Construct langfuse url

    Generates a direct link to your Langfox Cloud dashboard for any specific trace.

Set up in minutes

One URL. Then ask Langfuse Trace URL Extractor to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Langfuse Trace URL Extractor from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_mORUNaxsxJKt0DhLvO9C2dXdcem9Xgcsp3iXkEJx/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it Langfuse Trace URL Extractor, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable Langfuse Trace URL Extractor for the conversation.

Where the request belongs

Work Langfuse can move forward.

Built around the request

The DevOps engineer or ML engineer who spends too much time parsing logs at midnight. It is for anyone managing LLM observability and tired of manual URL construction.

01

ML Engineer

Analyzing trace performance and latency patterns during model evaluation.

02

DevOps Engineer

Debugging production errors by quickly jumping from error logs to traces.

03

AI Developer

Verifying that prompt inputs and outputs match expected schemas in real-time.

Bring your own AI

Change the model, client or framework. Keep Langfuse connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about Langfuse.

The practical details behind the request, access and result.

How can I use Langfuse Trace URL Extractor to find errors faster?

You can point your AI agent at any raw log file. The MCP will automatically pull the trace IDs and provide a clickable link that takes you straight to the error in Langfuse Cloud.

Does Langfuse Trace URL Extractor work with other observability capabilities?

This capability is specifically designed for Langfuse payloads. It will not work correctly with logs from other tracing platforms unless they use the same ID structure.

Can Langfuse Trace URL Extractor help me validate my logs?

Yes, it includes a capability to check if your JSON data contains all the required fields needed for successful tracing and observability.

Do I need to manually set up anything for Langfuse Trace URL Extractor?

No setup is required beyond connecting the MCP via Vinkius. Once connected, your agent can immediately start parsing your existing logs.

Can this capability help me debug production LLM errors?

Absolutely. It bridges the gap between seeing an error in your production logs and viewing the full execution trace in your dashboard.

What does `extract_trace_identifiers` do?

It parses a Langfuse payload JSON to extract the root id and project_id fields.

How do I generate a clickable link?

Use the construct_langfuse_url capability with the extracted trace ID and project ID.

Can I verify if a payload is valid before processing?

Yes, the validate_payload_schema capability checks for the presence of required keys.

One connection away

Give your agent a direct line to Langfuse.

Connect Langfuse once. Keep it beside 6,100+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available