Skip to main content

Look up your contacts in VS Code

A contact is one person across everything Launch knows about them. With the MCP server connected, the agent can answer questions that otherwise mean exporting three CSV files and matching emails by hand.

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 of my waitlist signups are paying customers now?
  • What has [email protected] asked for, and is she paying?
  • List paying customers who came from Product Hunt.
  • Mark [email protected] as in talks and note that she wants SSO.

For “Which paying customers left feedback?” VS Code calls list_contacts with:

{
  "paying": true,
  "has_feedback": true,
  "limit": 10
}

Returned: Contacts with id, email, source, waitlist status, subscriber flag, feedback count, Stripe status, plan, MRR and stage, plus a cursor when there are more.

Contacts tools and arguments

list_contacts

Read-only

List people across waitlist, feedback, subscribers and Stripe

payingoptionalboolean
has_feedbackoptionalboolean
statusoptional"waiting" | "invited" | "unsubscribed"
sourceoptionalstring, max 255
stageoptional"potential" | "in_talks" | "customer" | "recurring" | "not_a_fit" | "inactive"
qoptionalstring, max 254Part of an email address.
limitoptionalnumber, 1–100
cursoroptionalstring

get_contact

Read-only

Get one person across every primitive

contact_idrequiredstring, max 64Contact id, e.g. "ct_...".

update_contact

Set a contact's stage or note

contact_idrequiredstring, max 64
stageoptional"potential" | "in_talks" | "customer" | "recurring" | "not_a_fit" | "inactive"
noteoptionalstring, max 5,000

Behaviour worth knowing

  • People are matched on normalised email: lowercase, +alias removed, dots ignored on Gmail.
  • update_contact changes only the stage and the note. It cannot change an email, a waitlist status or anything in Stripe, and a new note replaces the old one.
  • It works without Stripe connected; every contact then has Stripe status none.
  • On the Free plan only waitlist people are listed, in a single page.
  • A contact is removed when the person no longer exists in any source, for example after their signup is deleted.
  • MCP tools are only available in Agent mode, not in Ask or Edit mode.