Getting started with Oppy

· · 5 min read
View as Markdown Open in ChatGPT Open in Claude

Getting started with Oppy

How it works

  1. Paste this one line into Claude or ChatGPT:
Add https://mcp.oppy.pro/mcp as a remote MCP server, have me sign in to Oppy and approve access, then read the Oppy note "getting-started" through the Oppy MCP (manage_notes get) and follow it.
  1. It adds the server, you sign in to Oppy and approve access, then it reads this note and does the rest. Everything below is written to the AI.

Instructions for the AI

You’re connected to your user’s Oppy through the Oppy MCP. Your job is to turn their Oppy into a well-trained advisor for their business, available at scale, moving qualified people toward the conversion goal in a polished, intelligent, non-pushy tone. Build a fully autonomous pipeline that starts with their Oppy and is fed by you through the MCP.

Do this in order. Make sure you do not write or save anything to their Oppy until your user approves the persona library in step 5.

  1. Confirm the connection and get the basics. Run list_teammates. A successful tools list only proves the server is reachable, so make sure a protected read succeeds before you say you’re connected. If the account has more than one Oppy, ask which one is the main customer-facing Oppy and work on that one. Then ask, in one short numbered batch: who they are, what their business is, who their customers or ICP are, what the offer or program is and what the conversion goal is (a signed agreement, a booked appointment, a membership, whatever it is). Skip any question this note or the conversation already answers.

  2. Read their Oppy first. Pull its current prompt, knowledge base, memories, goals and recent conversations. Extract the ICP and every persona already defined there: who the person is, how long they’ve been doing what they do, their production or size, which segment they’re in, where they come from, tech comfort, personality and what motivates them. Note every rule, memory or goal that duplicates or conflicts with another. Put all of it in a short table so your user can see what their Oppy already knows.

  3. List what’s missing and what their Oppy still needs to be successful. Cover at least: which offers, programs or tiers exist and what qualifies someone for each, what the conversion goal is and what happens after it, the pricing, terms and numbers their Oppy is allowed to discuss, how leads reach their Oppy and where they come from, what counts as qualified and when a conversation gets handed to your user. Ask targeted questions to fill every gap, one numbered batch, short. Do not guess answers. Leave anything unanswered marked “needs [user’s first name]”.

  4. Mine their Gmail, Slack and any other connected source where they talk with customers. Strip all PII and skip personal mail. Use the personas from step 2 to guide the search. Pull the questions customers actually ask, the objections they raise and how your user answers them word for word, the cold outreach that got replies, the follow-up cadence, what tipped people to say yes and your user’s tone of voice. Map each finding to a persona. Where a persona has no real examples, say so instead of filling it in.

  5. Look up and learn the frameworks their Oppy needs before you write a word: consultative selling, discovery, objection handling, value-based selling, follow-up cadence and closing. Learn the trade language of their industry and how their customers think about the decision. Most Oppy customers are in real estate, so for a brokerage that means how agents think about switching brokerages, splits, caps, fees and GCI. Then build a persona library: who they are, what they ask, their objections and the answer that works, what moves them, when their Oppy should engage, when it should stay quiet and when it should escalate to your user. Show the persona library and wait for approval. This is the first gate. Nothing gets saved before it.

  6. Rewrite their Oppy’s prompt from scratch, built from the approved persona library. Hard rules only. No duplicate or conflicting rules, memories or goals. Include: a qualification framework, objection handling and cold outreach taken from your user’s real messages in their voice, the persona library and how their Oppy tells which persona it’s talking to, when to engage or not, when to escalate or not.

  7. Show the key prompt changes before you save anything. This is the second gate. Save only after your user says yes.

  8. Give a few example prompts your user can use to build automation rules and loops pointed at their Oppy (or at Account Concierge if list_teammates shows one on the account).

  9. Build 5 to 10 branded templates. Start every one from the Oppy letterhead template: read it through the MCP (manage_notes get, note “letterhead-template”). Mix 8.5x11 pages, single growing pages with interactive charts and full-bleed slide decks, with content that fits their industry (for real estate: listing flyers, property websites, market reports). Share each one unlisted by link. Only share app.oppy.pro links.

  10. Show off. Once the above is saved, demo what their Oppy can now do with a few quick wins: build one branded page from the template for something they need this week, draft one automation rule or loop and run it past them, summarize their recent conversations with next actions. Then suggest next steps in short bullets, five or six max.

Critical: never invent a number, name, quote or customer fact to fill a gap. Leave it marked “needs [user’s first name]” and move on.