Help Center
Go back to application
Help Center
Go back to application
Dashboard
KPI Dashboard
Alerts
Uptime
Events
Events DashboardEvents APIEvents App
Sessions
Session Analytics
Technology
Technology OverviewLoad TimeJavascript ErrorsFailed Calls
Segmentation
Segments ReportSegmentation Definitions
Impacted Revenue
Impacted Revenue
Frustration
Frustration Signals
Acquisition
Acquisition Tagging - dataLayerAcquisition Tagging - Open Graph and Schema.org
Integrations
Integrating Slack with Webeyez
Implementation
Tag ManagerShopify - Tag Manager + Customer EventsShopify Customer EventCSP - Content Security PolicyIP Whitelisting How to Implement Webeyez with OneTrustShopify bot detection white listing
AI
Webeyez MCP serverConnect to the Webeyez MCPConnect Claude to Webeyez MCPWebeyez AI Credits

Connect Claude to Webeyez MCP

Implementing Webeyez as a Custom MCP Connector in Claude

This guide covers how to connect Webeyez to Claude as a custom connector (remote MCP server), for both an individual (Pro/Max/Free) license and a Team/Enterprise license.

Background

Custom connectors let Claude talk to a remote MCP (Model Context Protocol) server over the internet. Once connected, Claude can call Webeyez's tools directly inside a conversation, for example, querying journey/session data, checking status of background analytics queries, or pulling session recording links, without you copying data back and forth manually.

A few things to know before you start:

  • Custom connectors are available on Free, Pro, Max, Team, and Enterprise plans. Free users are limited to one custom connector total.
  • Webeyez's tools include actions like starting background queries, checking their status, retrieving session recordings, and submitting feedback, mostly read/reporting actions, but review the tool list yourself before granting access.

Prerequisites

  • An active Webeyez account with login access. After the connector is added in Claude, you'll be prompted to authenticate to Webeyez via OAuth, so make sure you can sign in to Webeyez yourself before starting, since Claude will redirect you to Webeyez's own login screen to complete the connection.
  • For Team/Enterprise: your Claude organization must have an Owner or Primary Owner to complete the initial setup, regular members cannot add org-wide custom connectors themselves.

Setup for a Personal License (Free, Pro, or Max)

  1. Open Claude (web, desktop, or mobile) and go to Settings > Connectors.
  2. Click the "+" button, then "Add custom connector" at the bottom of the Connectors list.
  3. Enter:

Name: Webeyez
URL: https://api.app.webeyez.com/mcp
Advanced settings -> Oauth aclint ID: webeyez-mcp

  1. Click Add, then Connect. You'll be redirected to log in to Webeyez and approve the connection. This is a one-time OAuth consent step, Claude never sees your Webeyez password.
  2. Once connected, enable it per conversation via the "+" button in the composer > Connectors, and toggle Webeyez on.
  3. Test it by asking Claude something like "Use Webeyez - How many session did we have in the past week"

Note: Free-plan users can only have one custom connector active at a time, if you already use another custom connector, you'll need to remove it first (there's no in-place edit; removing and re-adding is how updates are made too).


Setup for a Team or Enterprise License

Team/Enterprise setup happens in two stages: an Owner/Primary Owner registers the connector for the organization, then individual members authenticate.

Stage A - Organization setup (Owner/Primary Owner only)

  1. Go to Organization Settings > Connectors.
  2. Click "Browse connectors" at the bottom, or "+" > "Add custom connector" if Webeyez won't appear in the directory browse list.
  3. Enter the same details as above:
    Name: Webeyez
    URL: https://api.app.webeyez.com/mcp
    Advanced settings -> Oauth aclint ID: webeyez-mcp
  4. Save/Add the connector. It now appears in your org's connector list with a "Custom" label, available for members to connect to.
  5. Optional but recommended: under "Organization Settings > Connectors", review whether to allow this connector's interactive/UI tool calls org-wide, and decide if you want to restrict it to specific teams.

Stage B - Member setup (each individual user)

  1. Each team member goes to Settings > Connectors.
  2. They'll see "Webeyez" listed with a "Custom" label (added by the Owner in Stage A).
  3. Click "Connect", and complete authentication with their own Webeyez credentials.
  4. Enable Webeyez per conversation the same way as the personal flow: "+" > Connectors > toggle Webeyez on.

Enterprise-managed auth: On Enterprise plans, an Owner can optionally authorize Webeyez once for the whole org (Organization Settings > Connectors > Enterprise-managed auth), so members inherit access automatically on first login instead of individually authenticating.


Using Webeyez Once Connected

With the connector enabled in a conversation, you can ask Claude things like:

  • "Ask Webeyez what is my conversion rate in the past week"
  • "Ask Webeyez what are the latest javascript errors that occured"
  • "Ask Webeyez what are the most common login failures"

Claude will call the relevant Webeyez tool automatically when your request maps to it, you don't need to name the tool explicitly, just describe what you want.


Was this article helpful?

Powered by Product Fruits