MEGA Challenge

Start here

1. Connect your harness

   Your harness is the AI agent you work with, for example Claude Code, Codex, Cursor or VS Code with Copilot. Paste this prompt into it. The agent adds the course's MCP server, tells you what the sign-in needs from you, and checks that the connection works.

   Setup promptCopy prompt

   I'm a student in the MEGA.dev course, and you are my AI agent (my harness). Connect yourself to the course's MCP server. This is my own request.
   
   - Server name: mega-challenge
   - URL: https://hq.mega.dev/mcp (Streamable HTTP, OAuth sign-in)
   - Setup notes for each client: https://hq.mega.dev/llms.txt
   
   1. If you can already call the tools of the mega-challenge server in this session (for example list-challenges), go to step 5.
   2. Add the server to your own MCP configuration, with the name and URL above. Use your client's own command or config file; https://hq.mega.dev/llms.txt has them for common clients. If you cannot add MCP servers yourself, tell me which client you are and give me the exact command or config. I will add it.
   3. Before the sign-in starts, tell me in a few lines what it asks of me: a browser opens the course sign-in page; I type the email I enrolled with; the course mails me a one-time link; I open it in that same browser within 15 minutes (pasted into its address bar if my mail app opens links elsewhere); then I press Sign in and Approve.
   4. A new server is often not loaded in a session that is already running. If you cannot call its tools now, tell me exactly how to reload your MCP servers or start a new session, and to paste this prompt again there. Do not call the URL yourself and do not run the OAuth flow by hand: your client's own sign-in does it. Never ask me to paste a callback URL to you.
   5. Call list-challenges. Tell me that the connection works, and list the titles it returns. Do not start a Challenge yet: I will send the next message.
   
   Write to me in plain technical English: short sentences, one idea each, one message per step.

   Your agent cannot add servers itself, or you want to do it by hand? Open your client below. The server name is mega-challenge, and the URL is https://hq.mega.dev/mcp.

   Claude Code

   1. Add the server for all your projects. Run this in a terminal:

      claude mcp add --transport http mega-challenge --scope user https://hq.mega.dev/mcp

      Copy

   2. Sign in. Run this, then finish the sign-in in the browser that opens:

      claude mcp login mega-challenge

      Copy

   3. Or sign in from a Claude Code session: type /mcp, select mega-challenge, and follow the steps in your browser. If mega-challenge is not in the list, start a new session.

   Checked on 2026-10-09 against the Claude Code docs.

   Codex CLI

   1. Add the server. Run this in a terminal:

      codex mcp add mega-challenge --url https://hq.mega.dev/mcp

      Copy

   2. Sign in. Run this, then finish the sign-in in your browser:

      codex mcp login mega-challenge

      Copy

   3. To check, type /mcp in the codex terminal UI. It lists your active servers.

   Checked on 2026-10-09 against the Codex CLI docs.

   Cursor

   1. Open ~/.cursor/mcp.json (make the file if it does not exist) and add the server. If the file already has servers, add only the mega-challenge entry inside mcpServers:

      {
        "mcpServers": {
          "mega-challenge": {
            "url": "https://hq.mega.dev/mcp"
          }
        }
      }

      Copy

   2. Open Customize in the Cursor sidebar and find mega-challenge. When Cursor asks you to sign in to it, do so in the browser that opens.

   3. No connection? Open the Output panel (Cmd+Shift+U) and select "MCP Logs".

   Checked on 2026-10-09 against the Cursor docs.

   VS Code (GitHub Copilot)

   1. Open the Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows and Linux) and run MCP: Open User Configuration. Add the server inside servers:

      {
        "servers": {
          "mega-challenge": {
            "type": "http",
            "url": "https://hq.mega.dev/mcp"
          }
        }
      }

      Copy

   2. Save the file. When VS Code asks, confirm that you trust the server. On the first connection, VS Code opens a browser window for the sign-in.

   3. To start it or read its log, run MCP: List Servers, select mega-challenge, and choose an action.

   Checked on 2026-10-09 against the VS Code (GitHub Copilot) docs.

   Claude Desktop

   1. Go to Customize > Connectors. Click + Add, then Add custom connector.

   2. Enter the name mega-challenge and this remote MCP server URL, then click Continue:

      https://hq.mega.dev/mcp

      Copy

   3. Keep the authentication settings Claude found and click Continue. Under Authentication, choose Sign in now. Under OAuth client, choose Register automatically. Click Add, then finish the sign-in in your browser.

   4. In a chat, click + (lower left), then Connectors, and turn on mega-challenge.

   5. Claude connects to the server from Anthropic's cloud, not from your computer. On the Free plan you can add one custom connector.

   Checked on 2026-10-09 against the Claude Desktop docs.

   Another client? Add the URL as a remote (Streamable HTTP) MCP server, the way its docs say. After you add a server, reload your client's MCP servers or start a new chat: a running session often does not see a new server.

2. Sign in

   The first time your harness uses the server, it asks you to sign in. This is what happens:

   1. Your harness opens the course sign-in page in a browser. Some print a link instead: open it.
   2. Type the email you enrolled with. Only that address gets a link.
   3. Open the link from the mail in that same browser, within 15 minutes. It works once. If your mail app opens links in another browser, copy the link and paste it into the address bar of the sign-in browser.
   4. Press Sign in, then Approve to let your harness in.

   Already signed in to this site in that browser? Then you skip the email and only approve.

   Did the sign-in end on a 127.0.0.1 or localhost page that does not load? Then your harness was not listening. Reload it and sign in again from its own button. Do not paste that address to your agent in the chat.

   To see the Challenges on this site too, log in here with the same email.

3. Start a Challenge

   When the connection works, open the Challenges page and copy the starter prompt there. Start a new chat with your harness and paste it as the first message. It names no Challenge: your harness finds the open ones and tells you what one asks of you both.

   After the solve, your harness writes a debrief. Read it on the Challenge's page, then ask your harness what changed in your setup.