Use STUD with Claude

Three minutes from a terminal or the Claude app to your first run. Claude connects to STUD at one address, signs in through your browser, and from then on works from your STUD workspace.

In Claude Code

Add STUD once for every folder, then sign in from inside a session.

In a terminal, add the server:claude mcp add --transport http --scope user stud https://stud.com/mcp
Start Claude Code in any folder, type /mcp, choose stud, and choose Authenticate. Your browser opens to STUD.
Sign in with your email or GitHub, and approve what Claude may do. Set the daily credit cap on the same screen.
Back in Claude Code, the STUD tools appear. Say what you want done, or ask what to run.

Without --scope user, Claude Code adds the server only to the folder you are in.

From a shell you can also sign in with:

claude mcp login stud

In the Claude apps and claude.ai

Custom connectors belong to your Claude account, so one connection serves claude.ai, the desktop app and the mobile apps.

Open Customize, then Connectors, then Add, then Add custom connector.
Name it STUD and enter the address https://stud.com/mcp, then continue.
Choose Sign in now. STUD opens, you sign in with your email or GitHub, and you approve what Claude may do.
Choose Add. STUD is now available in your conversations.

On the Free plan you can add one custom connector. On Team and Enterprise plans an owner adds it under Organization settings, Connectors, and each member then chooses Connect.

What to say first

Ask what to run. On a new workspace Claude says in a line what STUD does, then asks what you do, who it is for, and what stage you are at, one question at a time, and saves each answer on your yes. After the first answers it suggests a play and gives the reason.

Or name an area (“the distribution ones”) and Claude starts from that playbook, or describe the output you want and it finds the play.

Before any run Claude names the play and its cost in credits and waits for your yes. Credits are taken when the run starts; a failed check is not refunded and comes back with what to fix; credits return only if STUD is at fault.

If something is off

Claude Code lists stud as needing authentication: Type /mcp, choose stud, and authenticate again. A sign-in lasts until you disconnect it.
The browser did not open: Copy the address Claude Code shows into any browser. If the return to Claude Code fails, paste the full address of the page you land on back into the prompt.
A call is refused: The refusal names what to do next, and Claude follows it. A permission you left unticked can be granted by disconnecting Claude under Account, Connected apps, and signing in again.
Claude talks about the wrong business: Claude is told to answer from your STUD workspace only. If it reads from files instead, say “use STUD”, and tell us: it is a defect on our side.

Everything else, permissions and credits included: Use STUD with your AI