OpenTelemetry Trace Context Extractor Connector for AI agents.
1 live capability
Parse W3C headers to fix broken distributed traces.
Waiting for input…
Why people use OpenTelemetry Trace Context Extractor
Fix broken OpenTelemetry traces with Trace Context Extractor
With this MCP, you just drop the header into your chat. It instantly separates the trace ID from the parent ID so you can see exactly what was passed along.
What Vinkius changes
You stop manually parsing hex strings.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 6,100+ Connectors
- Real-world use case 01
Trace ID mismatch
A developer notices a gap in their Jaeger traces and uses the MCP to check if the incoming header matches the expected format.
- Real-world use case 02
Broken propagation
An engineer finds a trace that stops at the API gateway and uses this capability to verify the context passed to the next service.
- Real-world use case 03
Header validation
A developer wants to check if a specific W3C header string is properly formatted before updating their middleware configuration.
Complete set · 1capability
The complete OpenTelemetry Trace Context Extractor capability set.
These are the exact actions your AI can choose when you ask it to work with OpenTelemetry Trace Context Extractor.
01
1 capability in this set.
Part of 1 available through OpenTelemetry Trace Context Extractor.
- 01 Capability
Extract trace context
Parses W3 and TraceContext headers to reveal trace IDs and flags. It ensures your telemetry data is valid and readable.
Set up in minutes
One URL. Then ask OpenTelemetry Trace Context Extractor to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use OpenTelemetry Trace Context 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_dAVsjHLD9WdoxwkV4ZZidFSuQqmK24xnvHrcysll/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 OpenTelemetry Trace Context Extractor, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable OpenTelemetry Trace Context Extractor for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_dAVsjHLD9WdoxwkV4ZZidFSuQqmK24xnvHrcysll/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 OpenTelemetry Trace Context Extractor URL.
- Step 03
Save and start
Save the connection and enable OpenTelemetry Trace Context Extractor in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"opentelemetry-trace-context-extractor": {
"url": "https://edge.vinkius.com/vk_preview_dAVsjHLD9WdoxwkV4ZZidFSuQqmK24xnvHrcysll/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 OpenTelemetry Trace Context Extractor
Open Agent mode in chat and ask: "Using OpenTelemetry Trace Context Extractor, help me...". 1 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"opentelemetry-trace-context-extractor": {
"url": "https://edge.vinkius.com/vk_preview_dAVsjHLD9WdoxwkV4ZZidFSuQqmK24xnvHrcysll/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 OpenTelemetry Trace Context Extractor
Ask Copilot: "Using OpenTelemetry Trace Context Extractor, help me...". 1 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"opentelemetry-trace-context-extractor": {
"url": "https://edge.vinkius.com/vk_preview_dAVsjHLD9WdoxwkV4ZZidFSuQqmK24xnvHrcysll/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 OpenTelemetry Trace Context Extractor
Open Cascade and ask: "Using OpenTelemetry Trace Context Extractor, help me...". 1 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"opentelemetry-trace-context-extractor": {
"url": "https://edge.vinkius.com/vk_preview_dAVsjHLD9WdoxwkV4ZZidFSuQqmK24xnvHrcysll/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 OpenTelemetry Trace Context Extractor
Ask Cline: "Using OpenTelemetry Trace Context Extractor, help me...". 1 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add opentelemetry-trace-context-extractor --transport http "https://edge.vinkius.com/vk_preview_dAVsjHLD9WdoxwkV4ZZidFSuQqmK24xnvHrcysll/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 OpenTelemetry Trace Context Extractor
Ask Claude: "Using OpenTelemetry Trace Context Extractor, show me...". 1 tools are ready
Where the request belongs
Work OpenTelemetry can move forward.
For engineers who spend too much time staring at distributed traces trying to find where the context died.
Observability Engineer
Verifying that trace propagation is working correctly across microservices.
SRE
Investigating broken spans and context loss during high-latency incidents.
Backend Developer
Debugging request flows through complex service meshes and API gateways.
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse Connectors
OpenTelemetry TraceContext Validator
Validates W3C TraceContext and OpenTelemetry headers for distributed agent tracing.
OpenTelemetry Trace Latency Analyzer
Analyze OpenTelemetry traces to identify latency bottlenecks and critical path inefficiencies.
Langfuse Trace URL Extractor
Extract trace IDs and construct observability URLs from Langfuse payloads.
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.
Highlight (Session Replay & UX)
Streamline observability by ingesting raw logs, OTLP logs, and OTLP traces directly into Highlight for session replay and UX monitoring.
Honeycomb
Automate observability via Honeycomb. manage datasets, queries, and markers directly from any AI agent.
Bring your own AI
Change the model, client or framework. Keep OpenTelemetry 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 OpenTelemetry.
The practical details behind the request, access and result.
How can I use OpenTelemetry Trace Context Extractor to debug my logs?
You paste your raw headers into your AI client, and the MCP breaks them down into readable IDs and flags.
Does OpenTelemetry Trace Context Extractor work with any W3C header?
It is specifically designed for the W3C TraceContext format used in modern observability.
Can this help me find broken traces in my microservices?
Yes, by verifying that the trace ID and parent ID are being passed correctly from one service to another.
Will OpenTelemetry Trace Context Extractor catch invalid hex characters?
Yes, it uses strict validation to ensure your IDs are properly formatted 32-character hex strings.
Do I need to set up a complex environment for this MCP?
No, you just connect it via Vinkius and start parsing headers immediately in your preferred client.
What does this capability extract?
It extracts the trace ID, parent ID, and trace flags from a W3C TraceContext traceparent_header.
How does it validate the header?
It uses a strict RegExp pattern (version-traceid-parentid-flags) and verifies that the trace ID is 32 hex characters and not all zeros.
Is it compatible with standard W3C headers?
Yes, it is specifically designed to parse the traceparent header following the W3C TraceContext specification.
One connection away
Give your agent a direct line to OpenTelemetry.
Connect OpenTelemetry once. Keep it beside 6,100+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available