How to Use the Highlight (Session Replay & UX) MCP in VS Code Copilot

Q: How do we share the Highlight (Session Replay & UX) server config with our VS Code Copilot team?

Create a .vscode/mcp.json file in your repository root and commit it to Git. Every team member with VS Code 1.96+ and Copilot will automatically load the tools from this shared MCP configuration file.

Commit team-wide telemetry tools to Git and stream raw logs directly to Highlight using VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Highlight (Session Replay & UX) MCP to VS Code Copilot

Create your Vinkius account to connect Highlight (Session Replay & UX) to VS Code Copilot and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Highlight (Session Replay & UX) with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Share raw log tools across your VS Code Copilot team

The `ingest_raw_log` tool lets your development team stream unstructured console logs straight to Highlight from their VS Code Copilot chat. By committing the server config to your repo, every engineer gets access to instant log ingestion. When a developer encounters a local test failure, Copilot parses the terminal output and uploads it. This links local test failures to Highlight session replays, helping your team fix bugs faster.

Analyze distributed traces inside VS Code Copilot

The `ingest_otlp_traces` tool sends OpenTelemetry JSON traces to Highlight to map distributed transactions. When debugging complex backend flows, your team can ask Copilot to inspect the trace output directly in the editor. This team-wide setup runs through the shared workspace config, ensuring everyone uses the same telemetry pipeline. Copilot extracts span data from local runs and pushes it to Highlight to correlate with frontend user sessions.

Enforce project ID validation via this MCP Server

The `ingest_otlp_logs` tool processes structured OTLP logs, validating that each payload contains the mandatory `highlight.project_id` attribute. In VS Code Copilot, this ensures that developers on different microservices route logs to their specific dashboards. Your team's config handles these project IDs securely. Copilot checks the workspace settings, injects the correct project attribute, and safely transmits the structured JSON log payload.

Setup guide

Set up Highlight (Session Replay & UX) MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Highlight (Session Replay & UX) MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Highlight (Session Replay & UX) tools listed. Try asking: "List my recent Highlight (Session Replay & UX) transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "highlight-session-replay-ux-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Highlight. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Highlight (Session Replay & UX) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Highlight (Session Replay & UX) MCP in VS Code Copilot

Create a `.vscode/mcp.json` file in your repository root and commit it to Git. Every team member with VS Code 1.96+ and Copilot will automatically load the tools from this shared MCP configuration file.

Yes, if your workspace configuration is set up correctly, Copilot can call the MCP tools during headless container sessions or remote SSH development.

Yes, it does. VS Code Copilot handles authentication securely, and the MCP server runs in an isolated sandbox, ensuring your telemetry data is never exposed to external parties.

Ensure your JSON matches the standard OpenTelemetry log record format, and check that the `highlight.project_id` is present in the resource attributes before sending.

Your telemetry payloads, including project IDs and trace data, undergo transit-only processing. No information is stored on the server itself, as it functions strictly as a secure proxy to Highlight's ingestion API.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript