GET STARTED

The Claude connector

Kelvin is a remote MCP server. You add it once in Claude and work from there on the same projects, the same runs and the same rooms that are already yours.

What you need first

A Kelvin account inside an organization. Access is by named invitation: somebody already inside adds you.
To run anything, a Mac with the Kelvin app open and enrolled as a machine of the organization. That is what drives the app and records what happened.
To read, nothing beyond the account: projects, builds, scenarios, evidence and captures all answer with no Mac awake.

Add the connector

In Claude, open Settings and go to Connectors.Open Connectors in Claude
Choose “Add custom connector”.
Give it a name, and paste the Kelvin server URL.https://mcp.kelvincode.com/mcp

There is no client id and no secret to copy from anywhere: Claude registers itself, and authentication opens Kelvin's sign-in the first time you use the connector. It is the dashboard's sign-in, with the same membership behind it.

After signing in comes a screen that describes every power being asked for in a sentence, not in an identifier. Reading can be granted quietly; anything that writes goes through that screen.

What you can ask it for

Reading	The organization's projects, the builds and scenarios inside them, the state of a run, what it concluded, and the captures it sealed. None of that depends on a Mac being on.
Running	Start a scenario against a build, follow it while it moves, and cancel one that stopped being interesting — including one somebody else started. If no Mac in the organization is free, the run waits in the queue: that is an answer, not a failure.
Live rooms	List the open rooms, join one, see the frame that is on screen at that moment, ask for control of the app, tap and type while holding it, hand it back, mark a point on the screen without taking anybody's hands, and record a change proposal.

The agent signs in against your own membership: what it reaches is what you reach, never more than that.

What to ask on the first day

List my Kelvin projects and the most recent sealed evidence.
Run the checkout scenario on the latest build and tell me the verdict.
Join the live room that is open and show me the screen.
Ask for control of the app and tap the continue button.

Three things worth knowing first

Sealed is not verified. Sealed means the contents of the package were checked against the hashes the run declared on close — these bytes are these bytes. Who signed it is a different question, and the product does not confuse the two.

The room lives as long as the run does. It opens with a run, follows that attempt and closes with it; when it ends, what belonged to the room goes too — chat, proposals, tickets and seats.

Touching takes control, and control belongs to one at a time. You ask, you wait for the current action to finish, and you hold it for a short while that renews while you are using it. The presenter can take it back at any moment. Marking a point on the screen, that one takes nobody's hands.

Opening a live session stays a human decision, in front of the Mac: the connector joins a room that already exists and never creates one.