Connect Masterji to Claude

In Claude Code — the quickest way

Two commands, and on a Team account it needs no admin permission — unless your organisation has restricted MCP servers in Claude Code, which it can. In your terminal, not inside a Claude session:

claude mcp add --transport http masterji https://helpindiebuild.com/api/mcp/

That registers it. It is not connected yet — claude mcp list shows ! Needs authentication, which is the expected state at this point and not a failure. To sign in, start a session:

claude

1. At the Claude prompt, type /mcp and press Enter. On its own — anything after it is read as a sub-command, so /mcp masterji answers that masterji is not a recognised action.
2. A panel lists your servers. Select masterji and press Enter.
3. Choose Authenticate. A browser opens; sign in — Google, or your email and password — and allow the connection.
4. Back in the session, /mcp now shows masterji connected. Ask it for your status to check.

What happens next

Claude sends you to Masterji to sign in — Google, or your email and password — then to a consent screen that names, in plain words, the address your browser will be sent back to. Read that line before you allow it. Then five things appear in the chat: see where you stand, declare today's task, file tonight's proof, put a question to Masterji, and ask to open the next phase.

If the consent screen takes a while to appear the first time, that is the server waking rather than a step that failed — it can be twenty seconds. Wait it out rather than starting again.

The first thing worth saying, once it is connected:

Ask Masterji for my status.

Connect once you have a goal. Two things stay on the site: the workshop, for a builder without an idea yet, and screenshots — a link is proof Claude can file for you, an image is filed here. What Masterji stores has a row for the connection: what goes to Claude, and the sign-in it holds for you.

Or add it as a connector on claude.ai

Same server, added through the web app instead — what happens after you connect is the same, and is described above. Worth knowing before you start: on a Team or Enterprise account only an organisation Owner can add a custom connector, so if you are not one this route is closed to you and Claude Code above is not. Leave the Client ID and Client Secret fields empty wherever they appear — they are only for a client you registered yourself.

On Free, Pro or Max

1. Open Customize > Connectors on claude.ai.
2. Click Add custom connector.
3. Paste the server URL from the top of this page.
4. Click Add.

Free accounts get one custom connector. The + button in the chat box is a different thing — that is where you switch connectors on and off per conversation, once one has been added.

On Team or Enterprise

Only an organisation Owner can add a custom connector here. If you are not one, this route is closed to you and Claude Code above is not. The Owner adds it once; everyone else then connects to it.

1. The Owner opens Organization settings > Connectors.
2. Add, then Custom. If Claude asks which type, choose Web.
3. Paste the URL, then Add.
4. Everyone else opens Customize > Connectors, finds the one labelled Custom, and clicks Connect.

Why connect it rather than just ask Claude

Because the count that opens the next phase is kept in rows the conversation cannot write. A proof filed from a chat goes through the same endpoint this site calls, is read by the same judge, and is counted by the same code — so what you get in Claude is a second door onto the same record, not a version of it that can be talked around. The rest of that answer is on the questions page.

If a step here is wrong

Anthropic moves these screens, and this page was last checked against their documentation on 12 September 2026. If a step no longer matches what you see, tell us at cmahendra9999@gmail.com and it gets corrected.