Zight MCP Server lets MCP-compatible AI tools connect to Zight context. Once connected, your AI assistant can use information from Zight links to help summarize recordings, investigate customer issues, and prepare follow-ups or handoffs.
Server URL: https://mcp.zight.com/mcp
Before you start
You need:
- A Zight account.
- An AI app that supports remote MCP servers or custom connectors.
- Permission to add custom connectors in that AI app.
Set up in Claude Chat
Use this walkthrough for the Claude Chat connector flow.
Server URL: https://mcp.zight.com/mcp
Step 1: Open your cloud workspace.
Open your cloud workspace.
Step 2: Click Customize.
Click Customize.

Step 3: In the Customize section, go to Connectors.
In the Customize section, go to Connectors.

Step 4: Select Add Custom Connector.
Select Add Custom Connector.

Step 5: Enter a name for the connector and provide the required URL.
Name the connector “Zight” or “Zight MCP,” then enter https://mcp.zight.com/mcp as the connector URL.

Step 6: Click Connect to open the authorization flow.
Click Connect to open the authorization flow.

Step 7: Authorize MCP access in the production account.
Authorize MCP access in the production account.

Step 8: Return to your tool and start using Zight links in prompts to retrieve information.
Once connected, paste or reference a Zight link in your AI conversation and ask the assistant to use Zight context.

Step 9: Ask follow-up questions to continue using Zight tools for transcripts, logs, OCR data, and other context.
You can ask for transcripts, OCR, console logs, network logs, summaries, and follow-up analysis when those details are available on the Zight item.

Set up when your organization already added Zight MCP
If your company has already added Zight MCP as an organization connector, you may not need to manually add the server URL.
- Open Claude → Customize → Connectors.
- If the Directory modal opens, close it.
- Scroll to Not connected.
- Select Zight MCP or Zight MCP Custom Connector.
- Click Connect.
- Authorize Zight.
- Confirm it appears as connected.
Set up in Claude Code
Use Claude Code’s remote HTTP MCP setup:
claude mcp add --transport http zight https://mcp.zight.com/mcpThen authenticate if prompted and verify the server appears in Claude Code’s MCP list.
Example prompts
Use Zight MCP to review this Zight link. Summarize the recording, pull out key action items, and identify any open questions.Use Zight MCP to analyze this request-video submission. Look for transcript details, OCR, console logs, network errors, and environment context. Recommend the next support or engineering action.Use Zight MCP to turn this recording into a Jira-ready bug report with reproduction steps, observed behavior, expected behavior, evidence, and suggested priority.Troubleshooting
I only see the connector directory, not “Add custom connector”
Possible causes:
- Your Claude plan or workspace does not allow custom connectors.
- A Claude Team/Enterprise owner/admin needs to add or enable the connector first.
- You are in a product surface that handles connectors differently.
- Your Claude client has not received the custom connector rollout yet.
Try checking the main Connectors list under Not connected for Zight MCP or Zight MCP Custom Connector before manually adding the server URL.
I opened the MCP URL in my browser and saw an authorization error
That can be expected. The MCP endpoint requires authorization and should be added through an MCP-compatible AI app, not opened directly like a normal web page.
Authorization fails after clicking Connect
- Confirm you are signed into the correct Zight account.
- Retry in a fresh browser session.
- Check whether pop-up blockers or browser privacy settings are interfering.
- Confirm your AI app supports OAuth for remote MCP connectors.
- If it still fails, contact Zight Support with the AI app name, screenshot, and approximate timestamp.
Claude asks for permission before using Zight tools
That is normal. Review the tool request and allow it if you want Claude to use Zight context for that conversation.
Comments
0 comments
Please sign in to leave a comment.