--- name: vibedna-connector-install description: Connect your VibeDNA account to your AI. Paste this file into a chat with your AI and ask it to set it up. It explains each step, asks before changing anything, and fixes the usual snags. Nothing to download. --- # VibeDNA Connector: Setup Guide > **For the AI assistant reading this. These rules come before every step below:** > > 1. **One step at a time.** Explain what the step is and what it changes, in plain words, as if the user has never done this before. Then ask the question written in the step and wait for a clear yes. If the answer is no, skip it and say so. > 2. **Say what a command does before you run it.** Never run anything the user has not agreed to. > 3. **Never ask for a password, a key or a code in the chat.** Signing in happens in the user's browser, on vibedna.ai. The user presses Allow there. You never see their password and you do not need it. > 4. **Some steps only look.** When a step changes nothing, say "this only checks, it changes nothing." > 5. **If something looks wrong, stop and explain.** Everything here can be undone (see the table at the end). --- ## What this is The VibeDNA connector lets an AI work with a VibeDNA account: - see what the account owns and what its plan opens - read the journals it owns and apply them to the project in front of it, step by step - get download links for its Systems and tools when the user is ready to install (each link lasts 5 minutes) - show what else VibeDNA makes, only when the user asks It cannot buy anything, change the plan or see payment details. It works only on the account that signed in. **Address:** `https://vibedna.ai/api/mcp` It lives on vibedna.ai, not on the computer: nothing gets installed or kept running, and it uses no memory on the machine. --- ## Step 0: Which app is this? (only checks, changes nothing) **Explain it like this:** "The setup is a little different depending on where you use me. Let me check which one this is." Work out which one applies and tell the user: - **Claude on the web (claude.ai), the Claude desktop app or the phone app:** go to Path A. - **Claude Code** (in a terminal, or inside VS Code or another editor): go to Path B. - **Codex** (the Codex app, the `codex` terminal, or the Codex extension in an editor): go to Path C. - **Something else:** say that VibeDNA has tested the connector with Claude, and that other apps that accept "custom MCP connectors" with sign-in may work with the same address, but VibeDNA has not confirmed them yet. Offer to try Path A's idea in that app's connector settings, and stop if it fails. --- ## Path A: Claude on the web, desktop or phone You cannot click in the user's settings, so you guide them. Give one instruction at a time and wait for "done". **Explain it like this:** "Claude lets you add connectors yourself. It takes about five clicks, and every Claude plan can do it (the Free plan allows one custom connector)." 1. Open **Customize > Connectors** (https://claude.ai/customize/connectors). On a Team or Enterprise plan, an Owner adds it once in **Organization settings > Connectors** and then each member connects with their own account. 2. Click **Add custom connector**. Name it `VibeDNA` and paste `https://vibedna.ai/api/mcp`. 3. If Claude asks how it should identify itself (**OAuth client**), choose **Register automatically**. This matters: the other option does not work with VibeDNA's sign-in yet. 4. Click **Connect**. A VibeDNA page opens. Sign in with the email used on vibedna.ai and press **Allow**. 5. In a new chat, turn VibeDNA on from the **+** button, under **Connectors**. **CHECK:** ask the user to send "What do I have on VibeDNA?" in a chat with the connector on. The answer starts with "Signed in as" and their email. --- ## Path B: Claude Code ### B1. Add the connector **Explain it like this:** "This adds VibeDNA to my list of connectors. It is just an address, nothing is downloaded or left running on your computer." **Ask:** "Do you want VibeDNA only in this project, or in every project you open with me?" - Only this project: `claude mcp add --transport http vibedna https://vibedna.ai/api/mcp` - Every project: `claude mcp add --transport http -s user vibedna https://vibedna.ai/api/mcp` Say which command you will run, run it after the yes, then run `claude mcp list` (this only checks). The line for `vibedna` should say **Needs authentication**. ### B2. Make me load it **Explain it like this:** "I read my list of connectors when this chat starts, so I will not see VibeDNA until the chat is reopened." Ask the user to close this Claude chat or tab and open it again (in VS Code, close the Claude tab and open a new one, then reopen this conversation from the history). Do not suggest reloading the whole editor window. ### B3. Sign in **Explain it like this:** "Now you approve it with your VibeDNA account. This happens in your browser, so I never see your password." Ask the user to type `/mcp`, choose **vibedna** and pick **Authenticate**. The browser opens a VibeDNA page: sign in with the email used on vibedna.ai and press **Allow**. **CHECK:** call the `whoami` tool. It answers "Signed in as" and the email, plus the plan. --- ## Path C: Codex ### C1. Add the connector **Explain it like this:** "This adds VibeDNA to Codex's list of connectors. It is just an address, nothing is downloaded or left running on your computer. The Codex app, the terminal and the editor extension share this list, so it is done once." Say you will run `codex mcp add vibedna --url https://vibedna.ai/api/mcp`, run it after the yes, then run `codex mcp list` (this only checks): `vibedna` should be listed. ### C2. Sign in **Explain it like this:** "Now you approve it with your VibeDNA account. This happens in your browser, so I never see your password." Run `codex mcp login vibedna` after the yes. The browser opens a VibeDNA page: the user signs in with the email used on vibedna.ai and presses **Allow**. ### C3. Make Codex load it Ask the user to close Codex and open it again, then type `/mcp`: `vibedna` should be on the list. **CHECK:** call the `whoami` tool. It answers "Signed in as" and the email, plus the plan. --- ## If something goes wrong | What you see | Why | What to do | |---|---|---| | `vibedna` does not show up in `/mcp` after reopening the chat | Some editors do not load connectors added "only for this project" | Explain, ask, then add it to the project's `.mcp.json` instead: an entry `"vibedna": {"type": "http", "url": "https://vibedna.ai/api/mcp"}` inside `mcpServers`. Read the file first and keep everything already in it. Reopen the chat. | | **Pending approval** | Claude asks before using a connector that came from a project file | Reopen Claude Code in that folder: it asks whether to use the new connector from the project file. Say yes. | | **Dynamic Client Registration rejected** or a sign-in error that keeps coming back | Claude remembers a failed first attempt | Remove it and add it again (`claude mcp remove vibedna`, then the add command from B1), reopen the chat and sign in again. | | The emailed sign-in link says it was used or expired | Links work once and expire after an hour | Ask for a fresh link on the same page, or use **Continue with Google** if that is how the account was made. | | "Nothing bought one by one yet" but the user did buy something | The purchase is on a different email | Ask which email they used to pay. Sign out of vibedna.ai, sign in with that one and connect again. | | Download link no longer works | Links last 5 minutes | Ask the connector for a new one when the user is ready. | Still stuck: admin@vibedna.ai --- ## How to undo everything | What was done | How to undo it | |---|---| | Connector added in Claude (web, desktop, phone) | Customize > Connectors > VibeDNA > Remove | | Connector added in Claude Code | `claude mcp remove vibedna` (add `-s user` if it was added for every project) | | Connector added in Codex | `codex mcp remove vibedna` | | Entry added to a `.mcp.json` | Delete the `vibedna` entry from that file | | The permission given on vibedna.ai | Removing the connector in Claude disconnects it | --- ## First things to ask - "What do I have on VibeDNA?" - "Read the journal I bought and apply it to this project, one step at a time." - "Get the download for my System and walk me through the install." - "Open VibeGen for me."