Use STUD with Grok

Grok Bot connects to STUD with a sign-in, the same way the Claude apps do. A few minutes from the first message to the first run, without leaving the Bot.

In Grok Bot

Everything happens inside the Bot: the sign-in, the approval, and the return. You will read one code in your mail app.

In any Bot, say: Connect to stud.com/mcp. The Bot asks whether to add https://stud.com/mcp as a connector. Choose Yes, add it.
A card named stud appears with Authorize. Tap it, and STUD's sign-in opens inside the Bot.
Enter your email and choose Email me a code. Read the six digits in your mail app and type them into the Bot's page. The same code creates your account if you are new.
The approval screen says Connect Cursor to STUD. Cursor is the company behind Grok Bot, and the app registered itself under that name. Tick what the Bot may do, set the daily credit cap, and choose Authorize.
Back in the Bot, STUD is connected. Say what you want done, or ask what to run.

The connector belongs to your Grok Bot account, so every Bot on it can use STUD once one has connected.

If the Bot asks you to name the connector, name it STUD.

On grok.com and in the Grok CLI

On grok.com, Connectors, then New Connector, then Custom, and enter the address https://stud.com/mcp. Then sign in to STUD and approve, as above.

In the Grok CLI, add the server once, then sign in through your browser the first time a STUD tool is used:

grok mcp add --transport http stud https://stud.com/mcp

In the CLI's /mcps view, i authenticates a server that is still waiting on a sign-in.

What to say first

Ask what to run. On a new workspace the Bot asks a few short questions one at a time, what your company is called, what it does in a sentence, who it is for, and saves each answer to your workspace on your yes. After the first answers STUD suggests a play with the reason, and the Bot asks before spending any credits.

A play STUD computes comes back checked. For the rest, the Bot writes the output to STUD's brief and STUD checks it; a failed check comes back with what to fix and is not refunded; credits return only if STUD is at fault. A delivered run lands on STUD.com with its record, and the next play comes from the playbook the run started.

If something is off

The code did not arrive: Check the newest email; the subject starts with the code. Choose Send a new code. Codes and links share one allowance, five an hour per address.
The approval screen names Cursor: Expected. Grok Bot signs in with Cursor's app, and STUD shows the name an app claims, marked unverified because self-registered apps cannot be verified.
The Bot says it needs to authenticate again: Say Connect to stud.com/mcp again and tap Authorize on the card. A sign-in lasts until you disconnect it under Account, Connected apps on STUD.com.
The Bot talks about the wrong business: It is told to answer from your STUD workspace only. If it reads from elsewhere, say use STUD, and tell us: it is a defect on our side.

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