Skip to main content

MCP server for contacts

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.

Get an API key → Contacts API overview

Things to ask

  • 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.

One call, start to finish

You type: “Which paying customers left feedback?” The agent calls list_contacts with:

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

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

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.

Questions

Is this a CRM over MCP?
No. There are no deals, pipelines, tasks or outbound messages. It is a read view over data Launch already holds, with an optional stage and note.
How does feedback sent with only a user id get matched?
Through Stripe customer metadata. Name the metadata key that holds your user id when you connect Stripe, and feedback and notifications for that id show on the right contact.