Skip to main content

See which signup sources pay in VS Code

Signups are easy to count and customers are what matter. With attribution over MCP, the agent can tell you which source produced paying customers and then pull up what those customers asked for, in the same conversation.

VS Code's agent mode (GitHub Copilot Chat) loads MCP servers from .vscode/mcp.json. Inputs keep the key out of the file.

Setup

You need a secret key (nv_live_…) from Dashboard → API keys.

01Add the server to the workspace

.vscode/mcp.json

{
  "inputs": [
    {
      "type": "promptString",
      "id": "nordva-key",
      "description": "Nordva Launch secret key",
      "password": true
    }
  ],
  "servers": {
    "nordva": {
      "type": "http",
      "url": "https://mcp.nordva.dev",
      "headers": {
        "Authorization": "Bearer ${input:nordva-key}"
      }
    }
  }
}

VS Code prompts for the key the first time the server starts and stores it in its secret storage, so this file is safe to commit. Note that the top-level property is servers, not mcpServers.

02Check the connection

Run MCP: List Servers from the Command Palette and start nordva. In the Chat view, switch to Agent mode and check that the nordva tools are listed under the tools button. Ask it to run setup_check.

Then ask VS Code

  • Which waitlist source produced paying customers last month?
  • Was the Product Hunt launch worth it?
  • Who referred the most people who ended up paying?
  • Which campaign converts best, and what did those customers ask for?

For “Which source produced paying customers in the last 30 days?” VS Code calls get_attribution_report with:

{
  "group_by": "referrer",
  "period_days": 30
}

Returned: One row per source with signups, confirmed, invited, paying, ever paid and the signup-to-paying rate, plus current MRR and collected revenue per currency, and whether Stripe is connected.

Attribution tools and arguments

get_attribution_report

Read-onlyIndie and Builder

See which signup sources produce paying customers

group_byoptional"referrer" | "utm_source" | "utm_campaign" | "referral_code"
period_daysoptionalnumber, 1–3,650
limitoptionalnumber, 1–100

Behaviour worth knowing

  • It only covers people who signed up through a Launch waitlist form, page or widget. The tool description tells the agent to say so and not to present it as page analytics.
  • The agent is told not to rank sources by conversion rate when a source has only a handful of signups.
  • Without Stripe connected the funnel still works; paying is zero and the result explains why.
  • Grouping by referring site is on Indie. Grouping by UTM source, UTM campaign and referral code is on Builder.
  • MCP tools are only available in Agent mode, not in Ask or Edit mode.