For GitHub Copilot, Cursor, Claude & Windsurf

Ask Copilot what is broken on your site

Connect Harvv to Copilot in one step. Copilot reads your live friction findings, dead clicks, rage clicks, broken forms, right inside your editor, then helps you fix them.

Install in VS Code Manual setup
1

Generate your MCP token

The token scopes the connection to your account. Every request Copilot makes only ever sees your sites. The raw token is shown once, so copy it when it appears.

This token is shown once and is now in the config block below. Save it somewhere safe.
2

Add it to Copilot

Click Install in VS Code above and VS Code will prompt you for the token. Prefer to do it by hand? Create or open .vscode/mcp.json in your project and paste this:

{ "servers": { "harvv": { "type": "http", "url": "https://harvv.com/mcp", "headers": { "Authorization": "Bearer ${input:harvv_token}" } } }, "inputs": [ { "id": "harvv_token", "type": "promptString", "description": "Harvv MCP token", "password": true } ] }

Using the Copilot CLI, Cursor, Claude Desktop, Windsurf, or Zed instead? Same server, same token. Point any MCP client at https://harvv.com/mcp with header Authorization: Bearer YOUR_TOKEN.

On Lovable? Harvv is in the Connectors catalog. Open Connectors → Harvv, paste your token, done. Step-by-step at /install/lovable.

Writing a custom client, or want the full tool reference, response shapes, and 401 troubleshooting? See the MCP server docs.

3

Ask Copilot

Open Copilot in agent mode, enable the Harvv tools when prompted, and ask away.

You: Use Harvv to show the top friction on my site this week.
Copilot: Calling harvv.get_friction_findings... 1. Dead clicks on .add-to-cart (142 sessions affected) 2. Rage clicks on the mobile menu toggle (88 sessions) 3. Form abandonment at the email field on /checkout (61 sessions) Want me to open the file where .add-to-cart is wired so we can fix it?

Copilot sees your findings, not your logs

The Harvv MCP returns aggregated findings only: top friction patterns ranked by sessions affected, counts, and which pages are worst hit. It never returns raw event streams, individual user sessions, or any PII. The connection is read-mostly. The only tool that writes anything is the pixel installer. Nothing in the tool set can delete or change your analytics data.

What you can ask

Plain prompts, mapped to the right tool

› What is hurting my site this week?
Returns your top friction findings (dead clicks, rage clicks, slow pages, broken forms) ranked by sessions affected.
› List my Harvv sites.
Shows every site on your account with its name, domain, and pixel key.
› Open my dashboard for this site.
Gives Copilot a deep link straight into the Harvv UI for the site you mean.
› Is the pixel firing on staging?
Fetches the URL and confirms whether the Harvv pixel is live there.
› Add Harvv to this project.
Hands Copilot the install snippet and where to place it, so it can wire the pixel for you.
Questions

Common questions

What is this, exactly?

Harvv runs a Model Context Protocol (MCP) server scoped to your account. MCP is the open standard that lets AI assistants like GitHub Copilot call external tools. Once you add the Harvv MCP to Copilot, you can ask Copilot questions like "what friction is hurting my site this week" and it pulls the answer straight from your Harvv data, without you leaving the editor.

Which Copilot does this work with?

GitHub Copilot in VS Code (agent mode) and the GitHub Copilot CLI both support custom MCP servers. The same config also works in Cursor, Claude Desktop, Windsurf, and Zed. It is one standard config block; only the file you paste it into changes.

Can Copilot see my users' data or raw event logs?

No. The MCP returns aggregated findings only: top friction patterns ranked by sessions affected, counts, and which pages are worst hit. It never exposes raw event streams, individual user sessions, or any personally identifiable information. The same PII scrubbing that runs in the pixel applies before anything reaches the MCP. Copilot can interact with your findings, but it cannot pull your logs.

Can Copilot change my site through this?

The Harvv tools are read-mostly. Copilot can read your findings, list your sites, deep-link to your dashboard, and check whether your pixel is firing. The only write-oriented tool is the pixel install helper, and even it just returns the snippet plus where to place it: your coding agent writes the file, the Harvv server never touches your filesystem. Nothing in the tool set is destructive, and Harvv never ships code changes to your app on its own.

How do I get my token, and is it safe?

Sign in and click Generate token on this page. The token is scoped to your account only: every tool call filters to your sites and no one else's. The raw token is shown once. If it ever leaks, revoke it from your dashboard and generate a new one. Keep it out of committed config (the install button uses an input prompt so VS Code stores it for you instead).

What can I actually ask once it is connected?

Try: "Use Harvv to show the top friction on my site this week." "Which page has the most rage clicks?" "Is my Harvv pixel installed on staging?" "Open my Harvv dashboard for this site." Copilot picks the right Harvv tool, runs it, and explains the result in plain language next to your code.

I connected it but every tool returns 401. What now?

The connection itself is working (the auth check was reached); your token was rejected. Harvv tokens never expire, so a 401 means the token was revoked or is the wrong one. Generate a fresh token above and reconnect Harvv in your client. The 401 response carries a reason code (token_revoked, token_not_found, or wrong_scope) in error.data.reason and the WWW-Authenticate header. Full breakdown is in the MCP docs at /docs/mcp.

I use Lovable, not Copilot. Is this the right page?

Same MCP server, yes. On Lovable, Harvv is a first-class connector: open Connectors, pick Harvv from the catalog, and paste a token generated above. The Lovable-specific walkthrough is at /install/lovable, and the full tool reference is at /docs/mcp.