Langfuse Trace URL Extractor Connector for AI agents.
3 live capabilities
Turn raw Langfuse logs into clickable dashboard links.
Waiting for input…
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.
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
- 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.
- 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.
- 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.
01—03
3 capabilities in this set.
Part of 3 available through Langfuse Trace URL Extractor.
- 01 Capability
Extract trace identifiers
Pulls trace and project IDs out of raw JSON payloads so you do not have to hunt for them.
- 02 Capability
Validate payload schema
Checks if your JSON data actually contains the required fields before you try to process it.
- 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 previewAdvanced clients IDE · CLI
Claude · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_mORUNaxsxJKt0DhLvO9C2dXdcem9Xgcsp3iXkEJx/mcp - Step 01
Open Connectors
In Claude Web or Claude Desktop, open Settings and choose Connectors.
- Step 02
Add the URL
Choose Add custom connector, name it Langfuse Trace URL Extractor, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable Langfuse Trace URL Extractor for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_mORUNaxsxJKt0DhLvO9C2dXdcem9Xgcsp3iXkEJx/mcp - Step 01
Open MCP settings
On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
- Step 02
Add the URL
Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Langfuse Trace URL Extractor URL.
- Step 03
Save and start
Save the connection and enable Langfuse Trace URL Extractor in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"langfuse-trace-url-extractor": {
"url": "https://edge.vinkius.com/vk_preview_mORUNaxsxJKt0DhLvO9C2dXdcem9Xgcsp3iXkEJx/mcp"
}
}
} - Step 01
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
- Step 02
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
- Step 03
Save the file
Cursor will automatically detect the new Connector
- Step 04
Start using Langfuse Trace URL Extractor
Open Agent mode in chat and ask: "Using Langfuse Trace URL Extractor, help me...". 3 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"langfuse-trace-url-extractor": {
"url": "https://edge.vinkius.com/vk_preview_mORUNaxsxJKt0DhLvO9C2dXdcem9Xgcsp3iXkEJx/mcp"
}
}
} - Step 01
Create MCP config
Create a .vscode/mcp.json file in your project root
- Step 02
Add the server config
Paste the JSON configuration above
- Step 03
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
- Step 04
Start using Langfuse Trace URL Extractor
Ask Copilot: "Using Langfuse Trace URL Extractor, help me...". 3 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"langfuse-trace-url-extractor": {
"url": "https://edge.vinkius.com/vk_preview_mORUNaxsxJKt0DhLvO9C2dXdcem9Xgcsp3iXkEJx/mcp"
}
}
} - Step 01
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
- Step 02
Add the server
Paste the JSON configuration above into mcp_config.json
- Step 03
Save and reload
Windsurf will detect the new server automatically
- Step 04
Start using Langfuse Trace URL Extractor
Open Cascade and ask: "Using Langfuse Trace URL Extractor, help me...". 3 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"langfuse-trace-url-extractor": {
"url": "https://edge.vinkius.com/vk_preview_mORUNaxsxJKt0DhLvO9C2dXdcem9Xgcsp3iXkEJx/mcp"
}
}
} - Step 01
Open Cline MCP Settings
Click the Connectors icon in the Cline sidebar panel
- Step 02
Add remote server
Click "Add Connector" and paste the configuration above
- Step 03
Enable the server
Toggle the server switch to ON
- Step 04
Start using Langfuse Trace URL Extractor
Ask Cline: "Using Langfuse Trace URL Extractor, help me...". 3 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add langfuse-trace-url-extractor --transport http "https://edge.vinkius.com/vk_preview_mORUNaxsxJKt0DhLvO9C2dXdcem9Xgcsp3iXkEJx/mcp" - Step 01
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
- Step 02
Add the Connector
Run the command above in your terminal
- Step 03
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
- Step 04
Start using Langfuse Trace URL Extractor
Ask Claude: "Using Langfuse Trace URL Extractor, show me...". 3 tools are ready
Where the request belongs
Work Langfuse can move forward.
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.
ML Engineer
Analyzing trace performance and latency patterns during model evaluation.
DevOps Engineer
Debugging production errors by quickly jumping from error logs to traces.
AI Developer
Verifying that prompt inputs and outputs match expected schemas in real-time.
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse ConnectorsOpenTelemetry Trace Latency Analyzer
Analyze OpenTelemetry traces to identify latency bottlenecks and critical path inefficiencies.
OpenReplay
Debug web applications by inspecting user sessions, technical events, and project data directly from your AI agent.
Highlight (Session Replay & UX)
Streamline observability by ingesting raw logs, OTLP logs, and OTLP traces directly into Highlight for session replay and UX monitoring.
Rollbar
Connect your AI assistant to Rollbar to identify active bugs, review stack traces, trace code deployments, and manage error lifecycles without leaving the chat.
Dynatrace (APM and Observability)
Monitor and manage your Dynatrace environment. query metrics, track problems, manage entities, and automate observability workflows directly from your AI agent.
Sentry
Monitor errors and application health via Sentry. query issues, inspect events, audit releases and check alert rules directly from any AI agent.
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